Triple
T37442714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger lunar probe program |
E930462
|
entity |
| Predicate | Ranger7_impactDate |
P187821
|
FINISHED |
| Object | 1964-07-31 |
—
|
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: 1964-07-31 | Statement: [Ranger lunar probe program, Ranger7_impactDate, 1964-07-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Ranger7_impactDate Context triple: [Ranger lunar probe program, Ranger7_impactDate, 1964-07-31]
-
A.
managedYearsWithRangers
Indicates the span of years during which an entity held a managerial role with the Rangers organization.
-
B.
hasRangers
Indicates that an entity possesses, employs, or is associated with one or more rangers (such as guardians, wardens, or protective personnel).
-
C.
silverRanger
Indicates a relationship where an entity holds the role, identity, or designation of a "silver ranger" within a specified context or system.
-
D.
redRanger
Indicates that an entity has the role, identity, or designation of a "Red Ranger" within a given context or system.
-
E.
ascentStageImpactDate
Indicates the calendar date on which an ascent stage impacts a surface or target body.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.