Triple
T36454104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Instruments Calypso-based phones |
E898102
|
entity |
| Predicate | favoredFor |
P185523
|
FINISHED |
| Object | experimentation |
—
|
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: experimentation | Statement: [Texas Instruments Calypso-based phones, favoredFor, experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoredFor Context triple: [Texas Instruments Calypso-based phones, favoredFor, experimentation]
-
A.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
B.
favoredAttribute
Indicates that one entity prefers, prioritizes, or gives special positive weight to a particular attribute of another entity or object.
-
C.
favoredRegion
Indicates that one region is preferred or given special priority over others in a particular context.
-
D.
symbolicallyChosenFor
Indicates that an entity has been selected to represent or stand in for something else in a symbolic or emblematic way.
-
E.
showsFavorTo
Indicates that one entity demonstrates preference, kindness, or advantageous treatment toward another entity.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:10 p.m.