Triple
T26690373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippo Regius |
E672860
|
entity |
| Predicate | laterRetakenBy |
P170285
|
FINISHED |
| Object | Byzantines |
—
|
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: Byzantines | Statement: [Hippo Regius, laterRetakenBy, Byzantines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRetakenBy Context triple: [Hippo Regius, laterRetakenBy, Byzantines]
-
A.
retakenBy
chosen
Indicates that something previously held or controlled was taken back again by a specified entity.
-
B.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
C.
laterRetconnedAs
Indicates that an earlier element in a narrative or canon was subsequently redefined, replaced, or explained away by a later retcon as being something else.
-
D.
laterUsurpedBy
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
-
E.
laterRestored
Indicates that something previously altered, damaged, or removed was subsequently brought back to its earlier state 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 3:25 a.m.