Triple
T37665178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End rod |
E937804
|
entity |
| Predicate | canBePlacedOnTop |
P200174
|
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, canBePlacedOnTop, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePlacedOnTop Context triple: [End rod, canBePlacedOnTop, true]
-
A.
canBePlacedOn
chosen
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.
canBePlacedOnSide
Indicates that one entity is capable of being positioned or oriented on its side relative to another entity or surface.
-
D.
isToppedWith
Indicates that one entity serves as a topping placed on the surface of another entity.
-
E.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:18 p.m.