Triple
T34355041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcus Aurelius Antoninus Augustus |
E881695
|
entity |
| Predicate | broughtRelicTo |
P33453
|
FINISHED |
| Object | Rome |
—
|
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: Rome | Statement: [Marcus Aurelius Antoninus Augustus, broughtRelicTo, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtRelicTo Context triple: [Marcus Aurelius Antoninus Augustus, broughtRelicTo, Rome]
-
A.
relicBroughtBy
Indicates that a relic was transported or delivered to a location or context by a specific agent or entity.
-
B.
relicTraditionallyBroughtFrom
Indicates that a relic is customarily obtained or transported from a particular source or place according to tradition.
-
C.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
D.
broughtTo
chosen
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
E.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.