Triple
T8414039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ANSI/IEEE 1014 VMEbus |
E198688
|
entity |
| Predicate | slotCountTypical |
P81866
|
FINISHED |
| Object | up to 21 slots |
—
|
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: up to 21 slots | Statement: [ANSI/IEEE 1014 VMEbus, slotCountTypical, up to 21 slots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slotCountTypical Context triple: [ANSI/IEEE 1014 VMEbus, slotCountTypical, up to 21 slots]
-
A.
typicalNumberOfSelections
Indicates the usual or expected count of selections made in a given choice or selection process.
-
B.
typicalSpindleCount
Indicates the usual or standard number of spindles associated with an entity in this relationship.
-
C.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
D.
tierCount
Indicates the number of distinct levels, ranks, or layers associated with an entity in a hierarchical or tiered structure.
-
E.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e328cc8190b3b038005d0bb66f |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:06 p.m.