Triple
T28521022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur |
E721764
|
entity |
| Predicate | settingConnection |
P62005
|
FINISHED |
| Object | post-space-mission life on Earth |
—
|
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: post-space-mission life on Earth | Statement: [Arthur, settingConnection, post-space-mission life on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingConnection Context triple: [Arthur, settingConnection, post-space-mission life on Earth]
-
A.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
-
C.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
settingRelation
chosen
Indicates a contextual relationship where one entity serves as the environment, backdrop, or situational context in which another entity exists or an event occurs.
-
E.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 3:20 a.m.