Triple
T5782096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THF |
E128181
|
entity |
| Predicate | formerlyServed |
P18982
|
FINISHED |
| Object | civil aviation |
—
|
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: civil aviation | Statement: [THF, formerlyServed, civil aviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyServed Context triple: [THF, formerlyServed, civil aviation]
-
A.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
C.
historicallyServedBy
Indicates that an entity was provided with services or support by another entity during a past period of time.
-
D.
garrisonServed
Indicates that a military unit or personnel were stationed at and performed service in a particular garrison or fortified location.
-
E.
officePreviouslyHeldBy
chosen
Indicates that a particular office or position was formerly occupied by a specified person or entity.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a17315881908aa12a830ba5f22b |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.