Triple
T12969630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia E70 |
E321357
|
entity |
| Predicate | supportsFlightMode |
P107841
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia E70, supportsFlightMode, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFlightMode Context triple: [Nokia E70, supportsFlightMode, true]
-
A.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
B.
hasFlySystem
Indicates that one entity (typically a venue or stage) is equipped with a fly system for lifting, lowering, and suspending scenery, lighting, or other stage elements.
-
C.
flightAbility
Indicates the capability or potential of an entity to fly or engage in powered or unpowered aerial movement.
-
D.
landingCapability
Indicates the ability or suitability of an entity (e.g., a vehicle or system) to perform a landing under specified conditions.
-
E.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97f1badac8190a59e60751f47b8d6 |
completed | April 10, 2026, 10:52 p.m. |
Created at: April 9, 2026, 8:34 p.m.