Triple
T36883601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sequoia |
E911546
|
entity |
| Predicate | becameOperationalYear |
P178233
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Sequoia, becameOperationalYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameOperationalYear Context triple: [Sequoia, becameOperationalYear, 2012]
-
A.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
-
B.
yearFirstOperational
chosen
Indicates the calendar year in which something first became operational or began functioning in its intended role.
-
C.
operatedInYear
Indicates that an entity was actively operating or functioning during a specified year.
-
D.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
E.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.