Triple
T10421275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lime Rock |
E245655
|
entity |
| Predicate | hasMaterialUse |
P1272
|
FINISHED |
| Object | local limestone used in construction |
—
|
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: local limestone used in construction | Statement: [Lime Rock, hasMaterialUse, local limestone used in construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialUse Context triple: [Lime Rock, hasMaterialUse, local limestone used in construction]
-
A.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
B.
hasPartUsed
Indicates that an entity utilizes another entity as a component or constituent part in its structure, function, or operation.
-
C.
hasProductionUse
Indicates that something is utilized or applied within a production or operational environment.
-
D.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
E.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2bee2081908e5e65df9100d463 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:11 p.m.