Triple
T37665177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End rod |
E937804
|
entity |
| Predicate | canBePlacedOnSide |
P200220
|
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: [End rod, canBePlacedOnSide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePlacedOnSide Context triple: [End rod, canBePlacedOnSide, true]
-
A.
canBePlacedOn
Indicates that one entity is allowed or able to be positioned or set on top of another entity.
-
B.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
-
C.
canSideWith
Indicates that one entity is able or permitted to align, cooperate, or take the side of another entity in a conflict, decision, or situation.
-
D.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
E.
hasASideOf
Indicates that one entity possesses or includes a particular side or face as part of its structure or boundary.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: May 3, 2026, 4:18 p.m.