Triple
T104588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosendale cement |
E2110
|
entity |
| Predicate | binderFor |
P5776
|
FINISHED |
| Object | sand |
—
|
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: sand | Statement: [Rosendale cement, binderFor, sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: binderFor Context triple: [Rosendale cement, binderFor, sand]
-
A.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
-
B.
isBackboneOf
Indicates that one entity forms the main supporting structure or central framework upon which another entity fundamentally depends.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
builder
Indicates that an entity is responsible for constructing, creating, or assembling another entity.
-
E.
embodiedBy
Indicates that an abstract concept, role, or function is physically or concretely realized in a specific entity.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.