Triple
T24791638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTP |
E620265
|
entity |
| Predicate | allowsManufacturerStylingCues |
P69527
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GTP, allowsManufacturerStylingCues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsManufacturerStylingCues Context triple: [GTP, allowsManufacturerStylingCues, yes]
-
A.
stylingEnables
Indicates that one entity provides or activates styling capabilities or visual formatting for another entity.
-
B.
usesProductionStyle
Indicates that one entity creates, presents, or operates another entity using a particular production style or method.
-
C.
styleRestriction
Indicates a constraint or limitation imposed on the manner, form, or stylistic way in which something may be expressed, presented, or performed.
-
D.
usedByManufacturer
Indicates that a manufacturer makes use of a particular resource, component, method, or tool in its production or operational processes.
-
E.
mayHoldStyle
chosen
Indicates that an entity is permitted or able to possess or be associated with a particular style or stylistic attribute.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:47 a.m.