Triple
T24577257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Portugal |
E608147
|
entity |
| Predicate | spectatorSafetyFocus |
P156402
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Rally Portugal, spectatorSafetyFocus, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectatorSafetyFocus Context triple: [Rally Portugal, spectatorSafetyFocus, high]
-
A.
spectatorAppeal
Indicates that an action, event, or entity is appealing, entertaining, or attractive to spectators or an audience.
-
B.
spectatorEnvironment
Indicates the environmental conditions or setting in which a spectator observes an event or activity.
-
C.
spectatorsFrom
Indicates that one or more spectators originate from, are associated with, or come to an event from a particular place or source.
-
D.
spectatorInterest
Indicates that one entity has an interest in observing, watching, or following another entity or event as a spectator.
-
E.
spectatorUse
Indicates that an entity observes or experiences an event, activity, or object without directly participating in or interacting with it.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97be2ac8190aecf5e54a37e266a |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:29 a.m.