Triple
T25425125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Lake |
E637097
|
entity |
| Predicate | integratedSouthbridge |
P85930
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Apollo Lake, integratedSouthbridge, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedSouthbridge Context triple: [Apollo Lake, integratedSouthbridge, yes]
-
A.
hasSouthbridge
chosen
Indicates that one hardware component includes or is connected to a southbridge controller as part of its architecture.
-
B.
hasNorthbridge
Indicates that an entity is equipped with or includes a northbridge component in its architecture.
-
C.
chipsetComponent
Indicates that one entity is a hardware component that forms part of, or is integrated into, a particular chipset.
-
D.
chipset
Indicates that one entity is the chipset (or is associated with the chipset) used by, contained in, or otherwise functionally related to another entity.
-
E.
integratedI_O
Indicates that one entity has integrated input/output functionality or operations with another entity, treating their I/O processes as a unified system.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bf25c881909f049d5393927bfb |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 1:57 p.m.