Triple
T2977584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSMAC ELF |
E80434
|
entity |
| Predicate | expansionCapability |
P32212
|
FINISHED |
| Object | video display add-ons |
—
|
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: video display add-ons | Statement: [COSMAC ELF, expansionCapability, video display add-ons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionCapability Context triple: [COSMAC ELF, expansionCapability, video display add-ons]
-
A.
expansionType
Indicates the specific manner or category by which something grows, extends, or increases in scope or size.
-
B.
hasExpansion
Indicates that one entity serves as a larger, extended, or elaborated form of another entity.
-
C.
expansionStatus
Indicates the current state or phase of growth, enlargement, or extension of something relative to its previous or intended size or scope.
-
D.
expandableCapacity
chosen
Indicates that an entity’s capacity can be increased beyond its initial or default level, typically through additional resources, components, or configuration.
-
E.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999b0d50819093dac7678b887a9b |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.