Triple
T4449771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E96378
|
entity |
| Predicate | hasOfficialOpeningDate |
P10845
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Submillimeter Array, hasOfficialOpeningDate, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialOpeningDate Context triple: [Submillimeter Array, hasOfficialOpeningDate, 2003]
-
A.
officialOpeningDate
chosen
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
C.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
D.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
E.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d5975c8190bfe8a2d5d2dbf075 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.