Triple
T37889540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Backdoor Pipeline |
E945087
|
entity |
| Predicate | typicalBoardType |
P71981
|
FINISHED |
| Object | shortboard |
—
|
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: shortboard | Statement: [Backdoor Pipeline, typicalBoardType, shortboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoardType Context triple: [Backdoor Pipeline, typicalBoardType, shortboard]
-
A.
hasBoardType
chosen
Indicates that an entity is associated with or uses a specific type or category of board.
-
B.
usesBoardShape
Indicates that one entity employs or is designed to work with a particular board shape as part of its function or configuration.
-
C.
mainBoardName
Indicates the name or designation assigned to a main board (e.g., primary circuit board or central hardware board) associated with an entity.
-
D.
boardProperties
Indicates a relationship where specific attributes or characteristics are assigned to or associated with a board.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.