Triple
T10857707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova 3 |
E256312
|
entity |
| Predicate | onboardFeatures |
P36407
|
FINISHED |
| Object | air conditioning |
—
|
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: air conditioning | Statement: [Nova 3, onboardFeatures, air conditioning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardFeatures Context triple: [Nova 3, onboardFeatures, air conditioning]
-
A.
hasOnboardFeature
chosen
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
B.
featuresIn
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
C.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
D.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
-
E.
onboardPlatform
Indicates that an entity is being added, integrated, or enrolled onto a particular platform so it can start operating or participating there.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751377da88190a7244bb9d6b0c2ec |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.