Triple
T11100006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDDF |
E262477
|
entity |
| Predicate | openness |
P97282
|
FINISHED |
| Object | open |
—
|
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: open | Statement: [UDDF, openness, open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openness Context triple: [UDDF, openness, open]
-
A.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
B.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
-
C.
openingMood
Indicates the emotional tone or atmosphere present at the beginning of an event, interaction, or narrative.
-
D.
openingEngagementOf
Indicates that one event, action, or interaction serves as the initial or first engagement within a larger sequence, context, or relationship involving another entity or event.
-
E.
initiallyOpenTo
Indicates that something starts out in an open state or condition at the beginning of a process, period, or interaction.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a29ee6c819092bc0da3f9255389 |
completed | April 9, 2026, 12:23 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.