Triple
T28474494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troesmis |
E720524
|
entity |
| Predicate | provinceAfterReforms |
P124980
|
FINISHED |
| Object | Scythia |
—
|
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: Scythia | Statement: [Troesmis, provinceAfterReforms, Scythia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provinceAfterReforms Context triple: [Troesmis, provinceAfterReforms, Scythia]
-
A.
countryAfterReform
Indicates that one country entity represents the state of that country after a specified reform or transformation has taken place.
-
B.
hasTerritoryReorganizedInto
chosen
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
C.
countryAfterCityRename
Indicates the country to which a city belongs after the city has undergone a renaming.
-
D.
partOfAdministrativeDivisionReform
Indicates that an entity is involved in, or results from, a reorganization or restructuring of administrative divisions.
-
E.
regionBeforeReform
Indicates that a region is defined or considered as it existed prior to a specific reform or reorganization.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 2:51 a.m.