Triple
T19070613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boedromia festival |
E466779
|
entity |
| Predicate | meaningOfEpithetBoedromios |
P114535
|
FINISHED |
| Object | helper in distress |
—
|
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: helper in distress | Statement: [Boedromia festival, meaningOfEpithetBoedromios, helper in distress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfEpithetBoedromios Context triple: [Boedromia festival, meaningOfEpithetBoedromios, helper in distress]
-
A.
hasMeaningOfEpithet
chosen
Indicates that one entity expresses or conveys the meaning or sense of another entity’s epithet.
-
B.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
languageOfEpithet
Indicates the language in which an epithet (such as a descriptive or honorary title) is expressed.
-
D.
epithetScope
Indicates that an epithet (a descriptive label or phrase) applies specifically within a defined contextual scope or domain for the referenced entity or relation.
-
E.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19ea01c8190b9bb789da32f9a90 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.