Triple
T2600866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia X |
E58338
|
entity |
| Predicate | cellularTechnology |
P36910
|
FINISHED |
| Object | 3G |
—
|
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: 3G | Statement: [Nokia X, cellularTechnology, 3G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellularTechnology Context triple: [Nokia X, cellularTechnology, 3G]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
connectivityFeatures
chosen
Indicates the types of network or communication options that are available or supported for connecting to or through an entity.
-
C.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
-
D.
networkCharacteristic
Indicates a relationship where a specific property or feature is attributed to a network or networking context.
-
E.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.