Triple
T7253281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IceCube Neutrino Observatory |
E157655
|
entity |
| Predicate | fullOperationStartDate |
P288
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [IceCube Neutrino Observatory, fullOperationStartDate, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullOperationStartDate Context triple: [IceCube Neutrino Observatory, fullOperationStartDate, 2011]
-
A.
fullOperationDate
Indicates the date on which an operation or process is fully carried out or becomes completely effective.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
-
D.
fullLineOpeningDate
Indicates the date on which an entire line (such as a route, service, or system) was officially opened for operation.
-
E.
partnerStartDate
Indicates the date on which the partnership or partner relationship between the entities begins.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.