Triple
T24577248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally Portugal |
E608147
|
entity |
| Predicate | typicalRallyCenter |
P16368
|
FINISHED |
| Object | Exponor in Matosinhos |
—
|
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: Exponor in Matosinhos | Statement: [Rally Portugal, typicalRallyCenter, Exponor in Matosinhos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRallyCenter Context triple: [Rally Portugal, typicalRallyCenter, Exponor in Matosinhos]
-
A.
typicalRallyHQ
Indicates that a location serves as the usual or standard headquarters where a rally is organized or coordinated.
-
B.
relationToWorldRallyChampionship
Indicates how an entity is connected or related to the World Rally Championship (e.g., by participation, organization, or association).
-
C.
mobilizationCentre
Indicates a location where resources, personnel, or equipment are gathered and organized in preparation for deployment or coordinated action.
-
D.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another 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_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. |
Created at: April 18, 2026, 2:29 a.m.