Triple
T32916157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roden Crater |
E842016
|
entity |
| Predicate | primarySenseEngaged |
P10166
|
FINISHED |
| Object | vision |
—
|
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: vision | Statement: [Roden Crater, primarySenseEngaged, vision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySenseEngaged Context triple: [Roden Crater, primarySenseEngaged, vision]
-
A.
primarySense
chosen
Indicates that one sense or meaning of an entity is designated as its main or most central sense among possible alternatives.
-
B.
primaryEngagement
Indicates the main or most significant interaction, involvement, or relationship that an entity has with another entity or activity.
-
C.
primaryInteraction
Indicates the main or most significant interaction occurring between the involved entities.
-
D.
basicSense
Indicates that one entity represents the most fundamental or primary meaning or interpretation of another entity.
-
E.
secondarySense
Indicates that one sense or meaning of an expression is a secondary or less primary interpretation relative to another sense.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:19 a.m.