Triple
T31494269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hematite Ridge |
E803491
|
entity |
| Predicate | isTargetTypeOf |
P28232
|
FINISHED |
| Object | in situ rover investigation |
—
|
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: in situ rover investigation | Statement: [Hematite Ridge, isTargetTypeOf, in situ rover investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTargetTypeOf Context triple: [Hematite Ridge, isTargetTypeOf, in situ rover investigation]
-
A.
isOfStrongType
Indicates that an entity belongs to a category or classification considered particularly robust, intense, or highly potent within a given context.
-
B.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
C.
isClassOf
chosen
Indicates that one entity is a class or category to which another entity belongs or is an instance of.
-
D.
canBeTypeOf
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
E.
isPartOfType
Indicates that one type or category is a constituent or subset within a larger, encompassing type or category.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e76f98819084babaa80607b5ed |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:40 p.m.