Triple
T36899149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | court of Theodosius II |
E911979
|
entity |
| Predicate | successorCourt |
P78
|
FINISHED |
| Object | court of Marcian |
—
|
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: court of Marcian | Statement: [court of Theodosius II, successorCourt, court of Marcian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCourt Context triple: [court of Theodosius II, successorCourt, court of Marcian]
-
A.
createdSuccessorCourtTo
Indicates that one court was established to replace and take over the functions of another court.
-
B.
successor
chosen
Indicates that one entity directly follows another in an ordered sequence or position.
-
C.
successorDivision
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
D.
laterCourt
Indicates that one court decision or proceeding occurs at a later time than another court decision or proceeding.
-
E.
successorJurisdictionFunction
Indicates that one jurisdictional authority or function has been succeeded or taken over by another, establishing a continuity of jurisdictional responsibility.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: May 3, 2026, 4:13 p.m.