Triple
T29991001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacramento Gold Miners |
E761877
|
entity |
| Predicate | operatedInYears |
P82414
|
FINISHED |
| Object | 1993–1994 |
—
|
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: 1993–1994 | Statement: [Sacramento Gold Miners, operatedInYears, 1993–1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInYears Context triple: [Sacramento Gold Miners, operatedInYears, 1993–1994]
-
A.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
B.
operatedInYear
chosen
Indicates that an entity was actively operating or functioning during a specified year.
-
C.
operatedYearRound
Indicates that the subject entity functioned or was in operation continuously throughout the entire year, without seasonal closure.
-
D.
historicallyOperatedOn
Indicates that an entity has, at some point in the past, performed an operation or action upon another entity.
-
E.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: April 29, 2026, 6:38 p.m.