Triple
T21061703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Spirit Gold |
E518863
|
entity |
| Predicate | statusYearDefinition |
P131810
|
FINISHED |
| Object | calendar year |
—
|
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: calendar year | Statement: [Free Spirit Gold, statusYearDefinition, calendar year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusYearDefinition Context triple: [Free Spirit Gold, statusYearDefinition, calendar year]
-
A.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
-
B.
officialStatusStartYear
Indicates the year in which an entity first attained or began its official status or recognition.
-
C.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
D.
yearFormalized
chosen
Indicates the specific year in which the relationship, concept, or entity was officially established, recognized, or formalized.
-
E.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
- 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_69e0b505ef108190b25dd4033e2ff7eb |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6feb064a48190b892b78e27e8d0fa |
completed | April 21, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:38 p.m.