Triple
T6125313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldstone Deep Space Communications Complex |
E136580
|
entity |
| Predicate | inOperationSince |
P37159
|
FINISHED |
| Object | early 1960s |
—
|
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: early 1960s | Statement: [Goldstone Deep Space Communications Complex, inOperationSince, early 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inOperationSince Context triple: [Goldstone Deep Space Communications Complex, inOperationSince, early 1960s]
-
A.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
B.
inOperationFrom
chosen
Indicates that an entity (such as a facility, service, or system) is actively functioning or available starting from a specified point in time.
-
C.
inForceSince
Indicates that a rule, law, agreement, or condition has been officially in effect starting from a specified date or time.
-
D.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
-
E.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.