Triple
T4001192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Very Large Array |
E89416
|
entity |
| Predicate | fullOperationDate |
P53435
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Very Large Array, fullOperationDate, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullOperationDate Context triple: [Very Large Array, fullOperationDate, 1980]
-
A.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
-
B.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
C.
fullThroughRunningDate
Indicates that something remains fully valid, active, or in effect up to and including a specified running (end) date.
-
D.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
E.
fullLineOpeningDate
Indicates the date on which an entire line (such as a route, service, or system) was officially opened for operation.
- F. None of above. chosen
Provenance (4 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:34 p.m.