Triple
T29897056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSM Association Chairman’s Award |
E759306
|
entity |
| Predicate | organizerRepresents |
P179936
|
FINISHED |
| Object | mobile network operators |
—
|
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: mobile network operators | Statement: [GSM Association Chairman’s Award, organizerRepresents, mobile network operators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizerRepresents Context triple: [GSM Association Chairman’s Award, organizerRepresents, mobile network operators]
-
A.
organizerBase
Indicates that one entity serves as the primary or foundational organizer for another entity or event.
-
B.
organizers
Indicates that one or more entities are responsible for planning, coordinating, or managing an event, activity, or group.
-
C.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
D.
organizerInstanceOf
Indicates that an organizer entity is an instance of a specific organizer type or class.
-
E.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 29, 2026, 6:05 p.m.