Triple
T36083852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article III:2 |
E1043722
|
entity |
| Predicate | predecessorIn |
P97
|
FINISHED |
| Object | Article III:2 of GATT 1947 |
—
|
NE NERFINISHED |
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: Article III:2 of GATT 1947 | Statement: [Article III:2, predecessorIn, Article III:2 of GATT 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorIn Context triple: [Article III:2, predecessorIn, Article III:2 of GATT 1947]
-
A.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorInSuit
Indicates that one item directly precedes another in an ordered sequence within the same suit or category.
-
C.
predecessorInName
Indicates that one entity’s name directly precedes another entity’s name in an ordered naming sequence or convention.
-
D.
predecessorInConcept
Indicates that one concept temporally or logically comes before another in a sequence or developmental progression.
-
E.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 3, 2026, 4:08 p.m.