Triple
T33503690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onze de Setembre |
E858059
|
entity |
| Predicate | observanceStartDate |
P1160
|
FINISHED |
| Object | 09-11 |
—
|
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: 09-11 | Statement: [Onze de Setembre, observanceStartDate, 09-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceStartDate Context triple: [Onze de Setembre, observanceStartDate, 09-11]
-
A.
startYearOfCommonObservance
Indicates the year in which a particular observance, practice, or recognition began to be commonly or widely observed.
-
B.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
C.
dateObserved
chosen
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
D.
observanceMayVaryByYear
Indicates that the way an observance is recognized, scheduled, or practiced can differ from one year to another.
-
E.
observanceSetting
Indicates the context, environment, or circumstances in which an observance (such as a ritual, ceremony, or practice) takes place.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:38 a.m.