Triple
T4027127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Canadian Air Force ensign |
E83617
|
entity |
| Predicate | representsBranch |
P53519
|
FINISHED |
| Object | air force |
—
|
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 force | Statement: [Royal Canadian Air Force ensign, representsBranch, air force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsBranch Context triple: [Royal Canadian Air Force ensign, representsBranch, air force]
-
A.
definesBranch
Indicates that one entity specifies or establishes a particular branch or subdivision of another entity.
-
B.
presentInBranch
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
C.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
D.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
E.
openedAsBranchOf
Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaed37e48190844032e7e77163e0 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:36 p.m.