Triple
T32258270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBDD |
E824078
|
entity |
| Predicate | terminalNodeValues |
P107095
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [OBDD, terminalNodeValues, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalNodeValues Context triple: [OBDD, terminalNodeValues, 0]
-
A.
hasTerminals
chosen
Indicates that one entity possesses, contains, or is associated with one or more terminal points, endpoints, or terminal elements of another entity.
-
B.
terminusOnBranch
Indicates that one endpoint or terminal location lies on a specific branch or subsidiary segment of a larger structure or network.
-
C.
terminalName
Indicates the name or label assigned to a specific terminal or endpoint within a system or network.
-
D.
nodeStructure
Indicates a hierarchical or connected arrangement of nodes and the structural relationships between them.
-
E.
terminalLocation
Indicates the specific terminal or endpoint location associated with an entity or process.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 12:41 a.m.