Triple
T12987785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 17 |
E321813
|
entity |
| Predicate | roverOperator |
P107913
|
FINISHED |
| Object | ground controllers in the Soviet Union |
—
|
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: ground controllers in the Soviet Union | Statement: [Luna 17, roverOperator, ground controllers in the Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roverOperator Context triple: [Luna 17, roverOperator, ground controllers in the Soviet Union]
-
A.
roverFunction
Indicates that an entity serves as a rover and specifies the function, role, or operational purpose it performs.
-
B.
roverStatus
Indicates the current operational condition or state of a rover in relation to its mission or environment.
-
C.
roverName
Indicates that an entity is the name assigned to a particular rover.
-
D.
firstRover
Indicates that the subject is the first rover (e.g., chronologically or in sequence) relative to other rovers in a given context.
-
E.
operatesRocket
Indicates that one entity controls or pilots the operation of a rocket belonging to or used by another entity.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97f1badac8190a59e60751f47b8d6 |
completed | April 10, 2026, 10:52 p.m. |
Created at: April 9, 2026, 8:41 p.m.