Triple
T37920217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power T with wordmark |
E945931
|
entity |
| Predicate | featuresLetter |
P144859
|
FINISHED |
| Object | T |
—
|
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: T | Statement: [Power T with wordmark, featuresLetter, T]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLetter Context triple: [Power T with wordmark, featuresLetter, T]
-
A.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
B.
featuresSign
chosen
Indicates that an entity includes, displays, or incorporates a particular sign as part of its appearance, content, or design.
-
C.
featuresLeader
Indicates that one entity includes, presents, or highlights another entity in the role of a leader.
-
D.
featuresHero
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
E.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.