Triple
T6442023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Special-purpose Plane |
E138246
|
entity |
| Predicate | planeIndex |
P70651
|
FINISHED |
| Object | 0xE |
—
|
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: 0xE | Statement: [Supplementary Special-purpose Plane, planeIndex, 0xE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planeIndex Context triple: [Supplementary Special-purpose Plane, planeIndex, 0xE]
-
A.
planeNumber
Indicates that an entity is associated with a specific airplane identification number (such as a tail number or flight number).
-
B.
planeName
Indicates that an entity has a specific name assigned to a plane (such as an aircraft or geometric plane).
-
C.
associatedPlane
Indicates a relationship where one entity is linked or connected to a specific plane, typically as the plane it uses, refers to, or is defined with respect to.
-
D.
numberOfPlanes
Indicates the quantity of planes associated with or involved in a given entity or situation.
-
E.
locationOnAircraft
Indicates that one entity is physically situated on or within an aircraft.
- F. None of above. chosen
Provenance (4 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06989dfb88190b25ff8b2c53f3ced |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.