Triple
T29456661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice chip |
E747119
|
entity |
| Predicate | associatedWithChipset |
P168049
|
FINISHED |
| Object | AGA |
E204439
|
NE 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: AGA | Statement: [Alice chip, associatedWithChipset, AGA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithChipset Context triple: [Alice chip, associatedWithChipset, AGA]
-
A.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
-
B.
associatedWithFirmware
Indicates a relationship where an entity is linked or connected to specific firmware, such as being used by, dependent on, or relevant to that firmware.
-
C.
hasChipType
chosen
Indicates that an entity is associated with or uses a specific type or category of chip.
-
D.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
E.
supportsOnChipNetworking
Indicates that one entity provides or enables integrated networking capabilities directly on a chip for another entity.
- F. None of above.
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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a260c0e537c81909b6c6fa9e3a98662 |
completed | June 8, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 3:46 p.m.