Triple
T36598707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osrhoene |
E902865
|
entity |
| Predicate | annexedAsProvince |
P166838
|
FINISHED |
| Object | Roman province of Osroene |
—
|
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: Roman province of Osroene | Statement: [Osrhoene, annexedAsProvince, Roman province of Osroene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexedAsProvince Context triple: [Osrhoene, annexedAsProvince, Roman province of Osroene]
-
A.
laterAnnexedTo
Indicates that one entity was annexed by another entity at a later point in time, after its initial status or affiliation.
-
B.
annexedAs
chosen
Indicates that one entity has been incorporated into and made a formal part of another entity, typically losing its prior independent status.
-
C.
annexedInYear
Indicates that one entity was formally annexed or incorporated into another in the specified calendar year.
-
D.
annexedTerritory
Indicates that one political entity has formally incorporated another territory into its own sovereign domain.
-
E.
annexedDuring
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.