Triple
T38199823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars 7 |
E1009020
|
entity |
| Predicate | landerDesign |
P190283
|
FINISHED |
| Object | similar to Mars 6 lander |
—
|
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: similar to Mars 6 lander | Statement: [Mars 7, landerDesign, similar to Mars 6 lander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landerDesign Context triple: [Mars 7, landerDesign, similar to Mars 6 lander]
-
A.
cabDesign
Indicates the design characteristics or configuration of a vehicle’s cab as defined or specified by an entity.
-
B.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
C.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
D.
rocketFamilyDesigner
Indicates that one entity is the designer or creator of the family or series to which a particular rocket belongs.
-
E.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:30 p.m.