Triple
T31079576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Περὶ τοῦ στεφάνου |
E792062
|
entity |
| Predicate | civicBodyAddressed |
P832
|
FINISHED |
| Object | Athenian popular court |
—
|
NE NERFINISHED |
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: Athenian popular court | Statement: [Περὶ τοῦ στεφάνου, civicBodyAddressed, Athenian popular court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civicBodyAddressed Context triple: [Περὶ τοῦ στεφάνου, civicBodyAddressed, Athenian popular court]
-
A.
governmentBodyAddressed
chosen
Indicates that a particular government body is the one being directly addressed or targeted by a communication, action, or request.
-
B.
addressedBy
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
C.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
D.
headOfGovernmentAddress
Indicates the official address or location associated with the head of government of an entity.
-
E.
storyAddressedTo
Indicates that a story is specifically directed or intended for a particular recipient or audience.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695bc8634819097370cc73a63a4b6 |
completed | May 3, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.