Triple
T18445221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Edessa |
E450636
|
entity |
| Predicate | residualTerritoriesLostBy |
P131643
|
FINISHED |
| Object | 1150 |
—
|
LITERAL FINISHED |
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: 1150 | Statement: [County of Edessa, residualTerritoriesLostBy, 1150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residualTerritoriesLostBy Context triple: [County of Edessa, residualTerritoriesLostBy, 1150]
-
A.
lostTerritoryBy
Indicates that one entity has had control or ownership of a territory taken away by another entity.
-
B.
causedTerritorialLossesTo
Indicates that one entity was responsible for another entity losing control over some portion of its territory.
-
C.
lastTerritoriesConqueredBy
Indicates that the referenced territories are the most recent ones taken control of through conquest by a specified entity.
-
D.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
E.
lostSovereignty
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
- F. None of above. chosen
Provenance (4 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c15127881909d23b6dd45d7ccc9 |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:30 a.m.