Triple
T11603294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qormi |
E275185
|
entity |
| Predicate | hasLocalityDay |
P100551
|
FINISHED |
| Object | last Sunday of June |
—
|
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: last Sunday of June | Statement: [Qormi, hasLocalityDay, last Sunday of June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalityDay Context triple: [Qormi, hasLocalityDay, last Sunday of June]
-
A.
containsLocality
Indicates that one place or area geographically includes or encompasses another locality within its boundaries.
-
B.
hasTypeLocality
Indicates the specific geographic location where an entity (typically a species or specimen) was originally found and formally described.
-
C.
localTime
Indicates that a specific time value is expressed relative to a particular local time zone or locale, rather than in a universal or standardized time reference.
-
D.
localityCondition
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
E.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8954daa908190a8d532e43aa4a881 |
completed | April 10, 2026, 6:14 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.