Triple
T12604614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samothracian Mysteries |
E300944
|
entity |
| Predicate | attractedParticipantsFrom |
P30111
|
FINISHED |
| Object | Greek cities |
—
|
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: Greek cities | Statement: [Samothracian Mysteries, attractedParticipantsFrom, Greek cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attractedParticipantsFrom Context triple: [Samothracian Mysteries, attractedParticipantsFrom, Greek cities]
-
A.
attractsParticipantsFrom
chosen
Indicates that an event, activity, or organization draws or recruits participants originating from a specified place, group, or source.
-
B.
attractsCompetitorsFrom
Indicates that one entity draws or lures competitors away from another entity or location.
-
C.
attractedMerchantsFrom
Indicates that one entity drew or lured merchants away from another entity or location.
-
D.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
E.
attractsTeamsFrom
Indicates that an entity draws or pulls in teams from another specified entity or location.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:10 p.m.