Triple
T14814412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N80 |
E348272
|
entity |
| Predicate | codename |
P2980
|
FINISHED |
| Object |
N80
N80 is a Nokia smartphone from the mid-2000s known for its sliding design, advanced multimedia features, and early support for 3G connectivity.
|
E1120496
|
NE FINISHED |
How this triple was built (4 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: N80 | Statement: [Nokia N80, codename, N80]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N80 Context triple: [Nokia N80, codename, N80]
-
A.
N806
N806 is a regional road in the Netherlands that provides access to and from the town of Bunschoten.
-
B.
N8
N8 is a designated national highway route, commonly used to identify a major intercity road in certain countries’ transportation networks.
-
C.
N98
N98 is the ICAO airport code assigned to Boyne City Municipal Airport, a public general aviation facility serving Boyne City, Michigan.
-
D.
N98
N98 is the Federal Aviation Administration (FAA) location identifier assigned to Boyne City Municipal Airport in Michigan, United States.
-
E.
N84
N84 is a regional road that serves as a key junction route connecting to the town of Bastogne in Belgium.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: N80 Triple: [Nokia N80, codename, N80]
Generated description
N80 is a Nokia smartphone from the mid-2000s known for its sliding design, advanced multimedia features, and early support for 3G connectivity.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: N80 Target entity description: N80 is a Nokia smartphone from the mid-2000s known for its sliding design, advanced multimedia features, and early support for 3G connectivity.
-
A.
N806
N806 is a regional road in the Netherlands that provides access to and from the town of Bunschoten.
-
B.
N8
N8 is a designated national highway route, commonly used to identify a major intercity road in certain countries’ transportation networks.
-
C.
N98
N98 is the ICAO airport code assigned to Boyne City Municipal Airport, a public general aviation facility serving Boyne City, Michigan.
-
D.
N98
N98 is the Federal Aviation Administration (FAA) location identifier assigned to Boyne City Municipal Airport in Michigan, United States.
-
E.
N84
N84 is a regional road that serves as a key junction route connecting to the town of Bastogne in Belgium.
- F. None of above. chosen
Provenance (5 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe0e89c81908c0e1fe2bc3ebcfc |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24cca0b88190b20a6c7dd77b8146 |
completed | May 8, 2026, 6 p.m. |
| NEDg | Description generation | batch_69fe291c69fc8190b29d6d2ca89ce6ec |
completed | May 8, 2026, 6:19 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe29a093d0819092ae65dc66a3c190 |
completed | May 8, 2026, 6:21 p.m. |
Created at: April 10, 2026, 1:48 a.m.