Triple
T36105882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article III:3 |
E1044353
|
entity |
| Predicate | predecessorTextIn |
P97
|
FINISHED |
| Object | 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: GATT 1947 | Statement: [Article III:3, predecessorTextIn, GATT 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTextIn Context triple: [Article III:3, predecessorTextIn, GATT 1947]
-
A.
successorInText
Indicates that one text element directly follows another in the sequential order of a text.
-
B.
predecessor
chosen
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorInName
Indicates that one entity’s name directly precedes another entity’s name in an ordered naming sequence or convention.
-
D.
predecessorTitleContext
Indicates that the relationship specifies the contextual circumstances (such as role, period, or setting) under which a predecessor’s title is relevant or applies.
-
E.
intendedPredecessorOf
Indicates that one entity is meant or planned to come before another in a sequence, order, or process.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: May 3, 2026, 4:08 p.m.