Triple
T16691124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beagle 2 |
E405594
|
entity |
| Predicate | discoveryOfStatus |
P26043
|
FINISHED |
| Object | lander imaged on Martian surface in 2015 |
—
|
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: lander imaged on Martian surface in 2015 | Statement: [Beagle 2, discoveryOfStatus, lander imaged on Martian surface in 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfStatus Context triple: [Beagle 2, discoveryOfStatus, lander imaged on Martian surface in 2015]
-
A.
hasDiscoveryStatus
chosen
Indicates the current state or phase of discovery or identification associated with an entity.
-
B.
discoveryConfirmed
Indicates that a previously identified potential discovery has been verified as valid or true.
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
seeStatus
Indicates that one entity observes or becomes aware of the current state or condition of another entity or process.
-
E.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea99bac8190a6c559ed7b7d8ecd |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.