Triple
T104576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosendale cement |
E2110
|
entity |
| Predicate | productionMethod |
P859
|
FINISHED |
| Object | burning natural cement rock at relatively low temperature |
—
|
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: burning natural cement rock at relatively low temperature | Statement: [Rosendale cement, productionMethod, burning natural cement rock at relatively low temperature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionMethod Context triple: [Rosendale cement, productionMethod, burning natural cement rock at relatively low temperature]
-
A.
constructionMethod
Indicates the technique or process by which something is built, assembled, or created.
-
B.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
C.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
D.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
E.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_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. |
Created at: Feb. 28, 2026, 2:12 a.m.