Triple
T9516194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAN on Curiosity rover |
E229530
|
entity |
| Predicate | hostPlatformType |
P842
|
FINISHED |
| Object | Mars rover |
—
|
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: Mars rover | Statement: [DAN on Curiosity rover, hostPlatformType, Mars rover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostPlatformType Context triple: [DAN on Curiosity rover, hostPlatformType, Mars rover]
-
A.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
B.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
C.
hasPlatformType
chosen
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
D.
hostSystem
Indicates that one entity serves as the primary computing or operating environment in which another entity runs, is managed, or is contained.
-
E.
consideredPlatform
Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
- 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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd987eefec8190b0db1928776bf02b |
completed | April 1, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cca56a3d088190bdc16670678fb6c6 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.