Triple
T30015739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BeagleBone Black |
E762589
|
entity |
| Predicate | hasPRU |
P200817
|
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: [BeagleBone Black, hasPRU, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPRU Context triple: [BeagleBone Black, hasPRU, true]
-
A.
hasPP
Indicates that an entity is associated with a particular prepositional phrase (PP) that modifies or relates to it in a syntactic or semantic structure.
-
B.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
C.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
D.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
-
E.
hasPrimate
Indicates that one entity possesses, contains, or is associated with a primate.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69ffb120b9988190b6361c69265033c0 |
completed | May 9, 2026, 10:11 p.m. |
Created at: April 29, 2026, 6:45 p.m.