Triple
T11721418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telephone Communication Limited |
E278639
|
entity |
| Predicate | isMarketingRelated |
P100978
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Telephone Communication Limited, isMarketingRelated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarketingRelated Context triple: [Telephone Communication Limited, isMarketingRelated, true]
-
A.
hasMarketingTarget
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
-
B.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
C.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
D.
hasMarketingRole
Indicates that an entity holds a position or responsibility related to marketing activities within an organization.
-
E.
hasMarketingTheme
Indicates that an entity is associated with or characterized by a particular marketing theme or campaign concept.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:40 p.m.