Triple
T33751129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festas de Lisboa |
E864843
|
entity |
| Predicate | keyDateReason |
P9461
|
FINISHED |
| Object | feast day of Saint Anthony |
—
|
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: feast day of Saint Anthony | Statement: [Festas de Lisboa, keyDateReason, feast day of Saint Anthony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDateReason Context triple: [Festas de Lisboa, keyDateReason, feast day of Saint Anthony]
-
A.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
B.
dateSignificance
chosen
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
-
C.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
-
D.
reasonForEvent
Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
-
E.
concernsDate
Indicates that something is related or refers specifically to a particular date or point in time.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb8ffae48190a4244047eab033e4 |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:45 a.m.