Triple
T26377527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acer Nitro |
E660939
|
entity |
| Predicate | brandHierarchyLevel |
P93352
|
FINISHED |
| Object | below Acer Predator |
—
|
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: below Acer Predator | Statement: [Acer Nitro, brandHierarchyLevel, below Acer Predator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandHierarchyLevel Context triple: [Acer Nitro, brandHierarchyLevel, below Acer Predator]
-
A.
brandHierarchyRole
Indicates the hierarchical role or position that a brand holds within a broader brand structure or family (e.g., parent, sub-brand, endorsed brand).
-
B.
brandLevel
chosen
Indicates the hierarchical rank or tier of a brand within a defined brand structure or classification system.
-
C.
ringHierarchyLevel
Indicates the position or rank of an entity within a structured ring-based hierarchy.
-
D.
brandingLevel
Indicates the degree or intensity of branding applied or associated with an entity (e.g., product, service, or organization).
-
E.
orderHierarchy
Indicates a hierarchical ordering relationship where one entity is positioned above or below another in a structured sequence or chain of command.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61071a4c4819090729e0c9789cf21 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:02 p.m.