Triple
T20640706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalcidian League |
E507211
|
entity |
| Predicate | hadCommon |
P140874
|
FINISHED |
| Object | coinage |
—
|
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: coinage | Statement: [Chalcidian League, hadCommon, coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadCommon Context triple: [Chalcidian League, hadCommon, coinage]
-
A.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
-
B.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
D.
has
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
E.
hadNo
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad132ebc8190b557914cf31a9033 |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.