Triple
T37833322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 9290 Communicator |
E943264
|
entity |
| Predicate | regionVariantFor |
P11942
|
FINISHED |
| Object | North America |
—
|
NE NERFINISHED |
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: North America | Statement: [Nokia 9290 Communicator, regionVariantFor, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionVariantFor Context triple: [Nokia 9290 Communicator, regionVariantFor, North America]
-
A.
regionalVariantOf
chosen
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
-
B.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
countryVariant
Indicates that one entity is a country-specific variant or localized version of another entity.
-
D.
regionIs
Indicates that one entity is located within, belongs to, or is associated with a specified geographic or administrative region.
-
E.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a007899cadc8190a04edd503eaf6514 |
completed | May 10, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_6a0078493e088190b0c5047cbe75d304 |
completed | May 10, 2026, 12:21 p.m. |
Created at: May 3, 2026, 4:19 p.m.