Triple
T26728651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Davenport |
E673903
|
entity |
| Predicate | hasBionicChip |
P103353
|
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: [Adam Davenport, hasBionicChip, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBionicChip Context triple: [Adam Davenport, hasBionicChip, yes]
-
A.
hasOnChip
Indicates that one component or system includes another component integrated directly onto the same chip or integrated circuit.
-
B.
supportsOnChipNetworking
Indicates that one entity provides or enables integrated networking capabilities directly on a chip for another entity.
-
C.
hasHybridSystem
Indicates that an entity is equipped with or incorporates a hybrid system, typically combining two or more different technologies or power sources.
-
D.
hasHardware
chosen
Indicates that one entity possesses, includes, or is equipped with specific hardware components or devices.
-
E.
supportsNEON
Indicates that one entity provides or enables NEON (ARM Advanced SIMD) instruction set support for 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:43 a.m.