Triple
T26944075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Five |
E678590
|
entity |
| Predicate | notablePilotStatus |
P145082
|
FINISHED |
| Object | survived Battle of Yavin |
—
|
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: survived Battle of Yavin | Statement: [Red Five, notablePilotStatus, survived Battle of Yavin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePilotStatus Context triple: [Red Five, notablePilotStatus, survived Battle of Yavin]
-
A.
notablePilot
Indicates that an entity is a distinguished or noteworthy pilot associated with another entity (such as a vehicle, event, or organization).
-
B.
notablePilotOnRoute
Indicates that a particular pilot is notably associated with operating or having operated a specific route.
-
C.
hasPilotStatus
chosen
Indicates that an entity holds or is assigned a specific pilot-related status or role.
-
D.
notableInformationStatus
Indicates that there exists noteworthy or significant information about an entity and specifies the status or condition of that information (e.g., confirmed, unverified, disputed, or missing).
-
E.
isNotedByPilotsAs
Indicates that something is recognized, remarked upon, or specifically mentioned by pilots.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 27, 2026, 6:20 a.m.