Triple
T27467582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (test orbiter) |
E693215
|
entity |
| Predicate | transferredToIntrepidYear |
P102829
|
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: [Enterprise (test orbiter), transferredToIntrepidYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferredToIntrepidYear Context triple: [Enterprise (test orbiter), transferredToIntrepidYear, 2012]
-
A.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
B.
NiceTransferYear
Indicates that an entity’s transfer in a particular year is considered favorable, pleasant, or beneficial.
-
C.
takenOverInYear
Indicates that one entity assumed control or ownership of another entity in a specified calendar year.
-
D.
integratedYear
chosen
Indicates the year in which one entity was incorporated into, merged with, or formally added to another entity or system.
-
E.
movedToInYear
Indicates that an entity changed location or residence to a specified place in a particular year.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 12:52 p.m.