Triple
T235267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-2 incident of 1960 |
E4495
|
entity |
| Predicate | legalOutcomeForPilot |
P2931
|
FINISHED |
| Object | trial in Soviet Union |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: trial in Soviet Union | Statement: [U-2 incident of 1960, legalOutcomeForPilot, trial in Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalOutcomeForPilot Context triple: [U-2 incident of 1960, legalOutcomeForPilot, trial in Soviet Union]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
C.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
-
D.
departurePilot
Indicates that a pilot is responsible for operating or commanding the departing flight or vehicle.
-
E.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25cc9ab2c81909af278a07f86aa1e |
completed | Feb. 28, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69a25b5dc640819092669575731c393f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.