Triple
T4449770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E96378
|
entity |
| Predicate | hasFirstLightDate |
P14088
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Submillimeter Array, hasFirstLightDate, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstLightDate Context triple: [Submillimeter Array, hasFirstLightDate, 1998]
-
A.
expectedFirstLight
chosen
Indicates the anticipated time or occurrence of the first appearance of light, such as dawn or initial illumination, in a given context.
-
B.
hasFirstUndisputedSurfaceArrivalDate
Indicates that there is a specific date on which an entity is recognized as having first arrived at a surface without dispute.
-
C.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
D.
hasFirstProofYear
Indicates the year in which something was first proven or formally demonstrated to be true.
-
E.
hasFirstTerm
Indicates that an entity is associated with a specific first term in an ordered sequence, period, or series.
- 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.