Triple
T35158830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6030 |
E1015201
|
entity |
| Predicate | supportsOrganizer |
P103410
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia 6030, supportsOrganizer, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOrganizer Context triple: [Nokia 6030, supportsOrganizer, yes]
-
A.
supportsOrganizerFunctions
chosen
Indicates that an entity provides functionality or assistance that enables or enhances the operations and responsibilities of an organizer.
-
B.
supportsOrganization
Indicates that one entity provides assistance, resources, or advocacy that helps sustain or advance an organization.
-
C.
providedByOrganizer
Indicates that something (such as a resource, service, or information) is supplied or made available by the organizer.
-
D.
organizerRepresents
Indicates that an organizer acts on behalf of, or serves as the representative of, another entity in a given context.
-
E.
organizerBase
Indicates that one entity serves as the primary or foundational organizer for another entity or event.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.