Triple
T29245742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portorosso Cup triathlon |
E741436
|
entity |
| Predicate | organizerInStory |
P60750
|
FINISHED |
| Object | town of Portorosso |
—
|
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: town of Portorosso | Statement: [Portorosso Cup triathlon, organizerInStory, town of Portorosso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizerInStory Context triple: [Portorosso Cup triathlon, organizerInStory, town of Portorosso]
-
A.
organizationInStory
Indicates that an organization appears or plays a role within the context of a specific story.
-
B.
organizerInFiction
chosen
Indicates that an entity serves as an organizer or coordinating figure within a fictional context or narrative.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
ownerInStory
Indicates that one entity is the owner of another entity within the context or narrative of a specific story.
-
E.
storylineEvent
Indicates that one event occurs as a distinct step or component within a larger narrative or storyline.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 12:32 p.m.