Triple
T36896853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 2 ANS |
E911912
|
entity |
| Predicate | hasTrainingCurriculum |
P199065
|
FINISHED |
| Object | air navigation theory |
—
|
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: air navigation theory | Statement: [No. 2 ANS, hasTrainingCurriculum, air navigation theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingCurriculum Context triple: [No. 2 ANS, hasTrainingCurriculum, air navigation theory]
-
A.
hasTrainingFor
Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
-
B.
hasTrainingTrack
Indicates that an entity is associated with or assigned to a specific training track or program.
-
C.
hasTrainingPrograms
chosen
Indicates that an entity offers, provides, or is associated with one or more training programs.
-
D.
hasTrainingType
Indicates that an entity is associated with or characterized by a specific type or category of training.
-
E.
hasTrainingStructure
Indicates that an entity is associated with, or organized according to, a specific training framework, setup, or configuration.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 3, 2026, 4:13 p.m.