Triple
T1952444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Canada |
E42187
|
entity |
| Predicate | joinedAllianceOn |
P1904
|
FINISHED |
| Object | 1997-05-14 |
—
|
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: 1997-05-14 | Statement: [Air Canada, joinedAllianceOn, 1997-05-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedAllianceOn Context triple: [Air Canada, joinedAllianceOn, 1997-05-14]
-
A.
alliance
Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
-
B.
allianceMember
chosen
Indicates that an entity is a member or participant in a specific alliance or coalition.
-
C.
allianceCreated
Indicates that a formal cooperative relationship or partnership has been established between two or more parties.
-
D.
joinedUNTogetherWith
Indicates that one entity became a member of or affiliated with the University of North Texas together with another entity, at the same time or as part of the same event.
-
E.
changesAllianceOf
Indicates that one entity causes or initiates a change in the alliance or affiliation status of another 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3501d108190bc5cb23f53db4411 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.