Triple
T19133994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colophonian |
E468386
|
entity |
| Predicate | possibleCitizenship |
P117235
|
FINISHED |
| Object | polis of Colophon |
—
|
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 of Colophon | Statement: [Colophonian, possibleCitizenship, polis of Colophon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleCitizenship Context triple: [Colophonian, possibleCitizenship, polis of Colophon]
-
A.
mayHoldCitizenshipOf
Indicates that an entity is allowed or eligible to possess citizenship status of a specified country or jurisdiction.
-
B.
possibleCountryOfCitizenship
chosen
Indicates that an entity could plausibly be a country in which the person or agent may hold, or be eligible to hold, citizenship.
-
C.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
D.
laterCitizenship
Indicates that an entity acquired citizenship in a country or polity at a later point in time, after some earlier status or affiliation.
-
E.
acquireCitizenshipBy
Indicates the process or means by which an entity obtains or is granted citizenship through a specific method, action, or legal basis.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.