Triple
T119190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portugal Day |
E2406
|
entity |
| Predicate | mainLocationOfCeremonies |
P3231
|
FINISHED |
| Object | rotates among Portuguese 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: rotates among Portuguese cities | Statement: [Portugal Day, mainLocationOfCeremonies, rotates among Portuguese cities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLocationOfCeremonies Context triple: [Portugal Day, mainLocationOfCeremonies, rotates among Portuguese cities]
-
A.
ceremonyLocation
Indicates the place where a ceremony is held or takes place.
-
B.
ceremonyHeldOn
Indicates that a specific ceremony took place on a particular date or day.
-
C.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
D.
mainLocation
chosen
Indicates that one entity serves as the primary or central location associated with another entity.
-
E.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a25646d5088190a057989c32da3a90 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.