Triple
T36482938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-1 |
E898864
|
entity |
| Predicate | worldwideContext |
P45282
|
FINISHED |
| Object | early 1960s space race |
—
|
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 space race | Statement: [SA-1, worldwideContext, early 1960s space race]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldwideContext Context triple: [SA-1, worldwideContext, early 1960s space race]
-
A.
observedWorldwide
Indicates that something has been seen, recorded, or recognized in locations across the entire world.
-
B.
worldDefinitionInContext
chosen
Indicates that a particular definition of a term or concept is specified as it applies within a given context or situation.
-
C.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
D.
considersWorld
Indicates that one entity regards, evaluates, or takes into account another entity as a world or overall context.
-
E.
worldParallels
Indicates that one world, scenario, or context runs in parallel to another, sharing similar structures, events, or conditions without being identical.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 3, 2026, 4:10 p.m.