Triple
T11746347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunder Bluff |
E279289
|
entity |
| Predicate | hasFlightMaster |
P101125
|
FINISHED |
| Object | Thunder Bluff flight master |
—
|
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: Thunder Bluff flight master | Statement: [Thunder Bluff, hasFlightMaster, Thunder Bluff flight master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightMaster Context triple: [Thunder Bluff, hasFlightMaster, Thunder Bluff flight master]
-
A.
hasLockFlight
Indicates that one entity is associated with a specific lock flight, representing a relationship where the entity uses, contains, or is located at that sequence of canal locks.
-
B.
isMaidenFlightOf
Indicates that an event is the first-ever flight of a particular aircraft or spacecraft.
-
C.
isFlownOn
Indicates that an entity (such as a person or object) travels or is transported using a particular aircraft or airline as the means of flight.
-
D.
hasFlightTrainingActivity
Indicates that an entity is involved in or associated with a flight training activity.
-
E.
hasTalons
Indicates that an entity possesses talons as a physical feature.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50763a081908597da118bd0a64e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.