Triple
T30956726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio 2016 Olympic Torch Relay |
E788694
|
entity |
| Predicate | mottoRelated |
P135251
|
FINISHED |
| Object | A New World (Rio 2016 motto) |
—
|
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: A New World (Rio 2016 motto) | Statement: [Rio 2016 Olympic Torch Relay, mottoRelated, A New World (Rio 2016 motto)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoRelated Context triple: [Rio 2016 Olympic Torch Relay, mottoRelated, A New World (Rio 2016 motto)]
-
A.
mottoLinked
chosen
Indicates that a motto is associated with or linked to a particular entity.
-
B.
relatedToMotto
Indicates that one entity has an association or connection with a motto, such as embodying, expressing, or being defined by that motto.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
E.
mottoDerivedFrom
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:54 p.m.