Triple
T28775540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonine Wall |
E726521
|
entity |
| Predicate | laterAbandonedInFavorOf |
P49004
|
FINISHED |
| Object | Hadrian's Wall |
—
|
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: Hadrian's Wall | Statement: [Antonine Wall, laterAbandonedInFavorOf, Hadrian's Wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAbandonedInFavorOf Context triple: [Antonine Wall, laterAbandonedInFavorOf, Hadrian's Wall]
-
A.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
B.
discontinuedInFavorOf
chosen
Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
-
C.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
D.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
E.
laterUsurpedBy
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 28, 2026, 6:17 a.m.