Triple
T14919588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quincy granite quarries |
E371472
|
entity |
| Predicate | rawMaterialFor |
P22211
|
FINISHED |
| Object | government buildings |
—
|
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: government buildings | Statement: [Quincy granite quarries, rawMaterialFor, government buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rawMaterialFor Context triple: [Quincy granite quarries, rawMaterialFor, government buildings]
-
A.
materialFormedIn
Indicates that a material is created, produced, or formed within a specified process, environment, or context.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
D.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
E.
materialProvidedFor
chosen
Indicates that one entity supplies or makes available a material for use, processing, or incorporation by another entity or purpose.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:33 a.m.