Triple
T14279715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittheus |
E354010
|
entity |
| Predicate | governedCityStateType |
P113574
|
FINISHED |
| Object | polis |
—
|
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: polis | Statement: [Pittheus, governedCityStateType, polis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedCityStateType Context triple: [Pittheus, governedCityStateType, polis]
-
A.
governingCityState
Indicates that one city or state holds governing authority or administrative control over another specified region or entity.
-
B.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
C.
hasCityGovernmentType
Indicates the specific form or structure of municipal governance that administers a city.
-
D.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
E.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6585270c8190a717127b2f5dab3b |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.