Triple
T17517526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raspberry Pi Pico |
E426603
|
entity |
| Predicate | hasPio |
P127733
|
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: [Raspberry Pi Pico, hasPio, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPio Context triple: [Raspberry Pi Pico, hasPio, true]
-
A.
hasPit
Indicates that one entity possesses, contains, or is characterized by a pit or hollow space.
-
B.
hasPilotis
Indicates that a building or structure is elevated on pilotis (supporting columns or stilts), rather than resting directly on the ground.
-
C.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
D.
hasRIO
Indicates that an entity is associated with, or possesses, a specific Region of Interest (RIO) in a given context.
-
E.
hasPierFunction
Indicates that an entity serves the role or function of a pier, such as providing a structure that extends over water for access, docking, or related activities.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452615a8481909974e9855ea7a8e4 |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.