Triple
T9311670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonus |
E224019
|
entity |
| Predicate | demoticStatus |
P88014
|
FINISHED |
| Object | deme with its own citizen register |
—
|
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: deme with its own citizen register | Statement: [Colonus, demoticStatus, deme with its own citizen register]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demoticStatus Context triple: [Colonus, demoticStatus, deme with its own citizen register]
-
A.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
B.
deciphermentStatus
Indicates the degree to which something (such as a text, code, or inscription) has been successfully decoded or interpreted.
-
C.
demarcationStatus
Indicates the current state or condition of how clearly and officially a boundary or division between entities is defined or marked.
-
D.
demiseOfStatus
Indicates the ending or loss of a previously held status, role, or condition for an entity.
-
E.
denominationStatus
Indicates the current recognition, validity, or standing of a particular denomination within a specified system or context.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ad3b20819092562c30e70a528f |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.