Triple
T37495997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger program |
E931828
|
entity |
| Predicate | firstLaunch |
P110715
|
FINISHED |
| Object | Ranger 1 |
E2226275
|
NE 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: Ranger 1 | Statement: [Ranger program, firstLaunch, Ranger 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunch Context triple: [Ranger program, firstLaunch, Ranger 1]
-
A.
firstInstallation
Indicates that an entity represents the earliest or initial installation event or instance associated with another entity.
-
B.
firstLaunchMission
chosen
Indicates that a mission is the first launch associated with a particular object, program, or entity.
-
C.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
D.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
E.
firstProductLaunch
Indicates that an entity is carrying out or associated with its initial product introduction to the market.
- F. None of above.
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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40952f5e6481908d35e29be188392a |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.