Triple
T22977346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District 12 |
E571361
|
entity |
| Predicate | citizensUse |
P55173
|
FINISHED |
| Object | tesserae for extra grain and oil |
—
|
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: tesserae for extra grain and oil | Statement: [District 12, citizensUse, tesserae for extra grain and oil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizensUse Context triple: [District 12, citizensUse, tesserae for extra grain and oil]
-
A.
civilianUse
Indicates that something is intended for, suitable for, or actually used by civilians rather than military or combat purposes.
-
B.
servesCitizensOf
Indicates that an entity provides services, support, or functions on behalf of the citizens of a specified place or jurisdiction.
-
C.
politicalUse
Indicates that something is used for political purposes, such as influencing, supporting, or opposing political actors, policies, or processes.
-
D.
municipalUse
Indicates that something is intended for, designated as, or used in connection with municipal or local government purposes.
-
E.
communityUsage
chosen
Indicates how something is used, adopted, or engaged with by a particular community or group of people.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.