Triple
T3071675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soccer United Marketing |
E64037
|
entity |
| Predicate | targetClients |
P481
|
FINISHED |
| Object | soccer leagues |
—
|
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: soccer leagues | Statement: [Soccer United Marketing, targetClients, soccer leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetClients Context triple: [Soccer United Marketing, targetClients, soccer leagues]
-
A.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
clientFor
Indicates that one entity acts as a client that uses the services, resources, or interface provided by another entity.
-
E.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.