Triple
T29065453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Stack |
E735660
|
entity |
| Predicate | hasNotableYearOfIntensiveUse |
P196924
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Operation Stack, hasNotableYearOfIntensiveUse, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableYearOfIntensiveUse Context triple: [Operation Stack, hasNotableYearOfIntensiveUse, 2015]
-
A.
hasNotableYear
Indicates that an entity is associated with a specific year that is particularly significant or noteworthy for it.
-
B.
hasNotableAnniversaryUse
Indicates that something is used or referenced in connection with a notable anniversary or commemorative milestone.
-
C.
yearOfSignificantUse
chosen
Indicates the specific year during which the subject was notably or prominently used, active, or in significant operation.
-
D.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: April 28, 2026, 10:17 a.m.