Triple
T31943750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_cb |
E815591
|
entity |
| Predicate | hierarchyProperty |
P173021
|
FINISHED |
| Object | |V_cb| ≫ |V_ub| |
—
|
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: |V_cb| ≫ |V_ub| | Statement: [V_cb, hierarchyProperty, |V_cb| ≫ |V_ub|]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hierarchyProperty Context triple: [V_cb, hierarchyProperty, |V_cb| ≫ |V_ub|]
-
A.
hierarchyLevelCode
Indicates the specific rank or position an entity holds within a defined hierarchy or organizational structure.
-
B.
hasHierarchyIn
Indicates that one entity occupies a higher or lower level within an ordered structure or chain of command relative to another entity in a specified context.
-
C.
structureProperty
Indicates that one entity has a structural attribute, feature, or characteristic that describes how it is organized or composed.
-
D.
isPartOfHierarchyWith
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
-
E.
hierarchyDepth
Indicates the level or distance of an entity from the top (root) within a hierarchical structure.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2d9aad88190a445f8f591cb19fc |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:06 a.m.