Triple
T9776023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CER Agreement |
E237248
|
entity |
| Predicate | predecessorAcronym |
P42598
|
FINISHED |
| Object | NAFTA (1965) |
—
|
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: NAFTA (1965) | Statement: [CER Agreement, predecessorAcronym, NAFTA (1965)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAcronym Context triple: [CER Agreement, predecessorAcronym, NAFTA (1965)]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
previousAbbreviation
Indicates that one abbreviation was used earlier or previously in place of another for the same entity or term.
-
C.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
D.
shortNameOfPredecessor
chosen
Indicates that an entity has a predecessor whose abbreviated or shorter name is being specified.
-
E.
abbreviationOfSuccessor
Indicates that one entity is an abbreviation or shortened form of another entity that is the successor in some sequence or versioning.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1325a988190a07a3dc4dce41cb3 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.