Triple
T30462682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reign of Macrinus |
E775053
|
entity |
| Predicate | locationOfKeyEvents |
P127335
|
FINISHED |
| Object | Antioch |
—
|
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: Antioch | Statement: [Reign of Macrinus, locationOfKeyEvents, Antioch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfKeyEvents Context triple: [Reign of Macrinus, locationOfKeyEvents, Antioch]
-
A.
significantEventPlace
chosen
Indicates the place where a significant event occurred or is associated with an entity.
-
B.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
C.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
D.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
E.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: April 29, 2026, 8:10 p.m.