Triple
T37653618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg Summit |
E937237
|
entity |
| Predicate | reviewedOutcomeOf |
P190117
|
FINISHED |
| Object | 1992 Rio Earth Summit |
—
|
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: 1992 Rio Earth Summit | Statement: [Johannesburg Summit, reviewedOutcomeOf, 1992 Rio Earth Summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewedOutcomeOf Context triple: [Johannesburg Summit, reviewedOutcomeOf, 1992 Rio Earth Summit]
-
A.
reviewOutcome
Indicates the result or conclusion reached after evaluating or reviewing something.
-
B.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
-
C.
hasBeenReviewedIn
Indicates that an entity has been evaluated or critiqued within a specific review, publication, or reviewing context.
-
D.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.