Triple
T36870099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Dacia |
E911202
|
entity |
| Predicate | evacuatedUnder |
P109226
|
FINISHED |
| Object | Emperor Aurelian |
—
|
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: Emperor Aurelian | Statement: [Roman Dacia, evacuatedUnder, Emperor Aurelian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuatedUnder Context triple: [Roman Dacia, evacuatedUnder, Emperor Aurelian]
-
A.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
B.
evacuatedDuring
chosen
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
C.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
-
D.
evacuatedGroup
Indicates that a group of entities has been removed from a location or situation for safety or emergency reasons.
-
E.
evacuationOrderedAfter
Indicates that an evacuation is officially ordered as a consequence of, and subsequent to, a specified prior event or condition.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.