Triple
T29245741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portorosso Cup triathlon |
E741436
|
entity |
| Predicate | runningSegmentLocation |
P124124
|
FINISHED |
| Object | streets of Portorosso |
—
|
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: streets of Portorosso | Statement: [Portorosso Cup triathlon, runningSegmentLocation, streets of Portorosso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runningSegmentLocation Context triple: [Portorosso Cup triathlon, runningSegmentLocation, streets of Portorosso]
-
A.
segmentLocation
chosen
Indicates the spatial or positional relationship specifying where a particular segment is located within a larger structure or context.
-
B.
trackSegment
Indicates a specific portion or section of a larger track or route that is treated as a distinct segment.
-
C.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
D.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
E.
runsDirection
Indicates that an entity moves or operates in a specified direction.
- 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_69f66489459c8190aa343cb2b8af1300 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:32 p.m.