Triple
T3406719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spencer |
E71790
|
entity |
| Predicate | hasNameDayInSomeRegions |
P910
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Spencer, hasNameDayInSomeRegions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameDayInSomeRegions Context triple: [Spencer, hasNameDayInSomeRegions, yes]
-
A.
hasNameDay
chosen
Indicates that an entity is associated with a specific date on which its name is traditionally celebrated (a name day).
-
B.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
C.
hasRegionalHolidayName
Indicates that a regional holiday is associated with a specific name or designation used to refer to it.
-
D.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
E.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8ec68c88190913df5f6cafad9e9 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.