Triple
T4249848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperCam |
E95820
|
entity |
| Predicate | firstOperatedOn |
P45365
|
FINISHED |
| Object | Perseverance landing date 2021-02-18 |
—
|
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: Perseverance landing date 2021-02-18 | Statement: [SuperCam, firstOperatedOn, Perseverance landing date 2021-02-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperatedOn Context triple: [SuperCam, firstOperatedOn, Perseverance landing date 2021-02-18]
-
A.
operatedOn
Indicates that one entity has performed a surgical or procedural operation on another entity.
-
B.
firstPerformedOn
chosen
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
-
C.
operatedFor
Indicates that one entity performed operations or provided services on behalf of, or in support of, another entity for a certain period or purpose.
-
D.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
E.
operatedBefore
Indicates that one entity performed an operation or action at an earlier time than 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9f11008190a0021e0ad730a79d |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.