Triple
T4922085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viking 1 |
E110487
|
entity |
| Predicate | missionDiscipline |
P60057
|
FINISHED |
| Object | planetary science |
—
|
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: planetary science | Statement: [Viking 1, missionDiscipline, planetary science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionDiscipline Context triple: [Viking 1, missionDiscipline, planetary science]
-
A.
spiritualDiscipline
Indicates a relationship where an entity engages in or practices a form of spiritual training, exercise, or regimen aimed at cultivating spiritual growth or character.
-
B.
sacramentalDiscipline
Indicates the rules, practices, and regulations governing how religious sacraments are properly administered and received.
-
C.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
-
D.
hasClericalDiscipline
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
-
E.
strongInDiscipline
Indicates that an entity possesses a high level of strength, skill, or proficiency in a particular discipline or field.
- F. None of above. chosen
Provenance (4 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffc2ab08190992db2400562bcee |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:30 p.m.