Triple
T1972935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman concrete |
E42841
|
entity |
| Predicate | bindingPhase |
P5784
|
FINISHED |
| Object | calcium-aluminum-silicate-hydrate |
—
|
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: calcium-aluminum-silicate-hydrate | Statement: [Roman concrete, bindingPhase, calcium-aluminum-silicate-hydrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingPhase Context triple: [Roman concrete, bindingPhase, calcium-aluminum-silicate-hydrate]
-
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.
phase
chosen
Indicates that one entity is in a particular stage, step, or phase within a process, sequence, or lifecycle relative to another reference.
-
C.
boundFor
Indicates that something is destined, directed, or scheduled to go toward a particular destination or target.
-
D.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
-
E.
hasPhaseRelation
Indicates that two entities are related by a specific phase difference or phase alignment in time or a cyclical process.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f477988190b0165fc46b1cccfd |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.