Triple
T20790261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plataean |
E511753
|
entity |
| Predicate | civicIdentity |
P92302
|
FINISHED |
| Object | citizen of Plataea |
—
|
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: citizen of Plataea | Statement: [Plataean, civicIdentity, citizen of Plataea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civicIdentity Context triple: [Plataean, civicIdentity, citizen of Plataea]
-
A.
hasCivicIdentity
chosen
Indicates that an entity possesses a recognized status, role, or affiliation within a civic, social, or political community.
-
B.
hasCivicNumber
Indicates that an entity is associated with a specific civic (street) number used for its address.
-
C.
citizenshipDocument
Indicates that there exists an official document that certifies or proves an entity’s citizenship status with respect to a state or country.
-
D.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
E.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28f0e1081909f18dddfc6ec084c |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:38 p.m.