Triple
T13138717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosalind Franklin rover |
E312152
|
entity |
| Predicate | drillCapability |
P39122
|
FINISHED |
| Object | up to 2 meters depth |
—
|
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: up to 2 meters depth | Statement: [Rosalind Franklin rover, drillCapability, up to 2 meters depth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drillCapability Context triple: [Rosalind Franklin rover, drillCapability, up to 2 meters depth]
-
A.
hasDrillHolesFrom
Indicates that an object bears drill holes that were created by another specified entity or process.
-
B.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
C.
notableDrill
Indicates that an entity is recognized as a significant or noteworthy drill, exercise, or practice activity in a given context.
-
D.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
E.
hasRefuellingCapabilityFor
Indicates that one entity is capable of providing or performing refuelling operations for another entity.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b6a4348190b9922ed255759078 |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:09 p.m.