Triple
T4849076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graff House |
E108365
|
entity |
| Predicate | hasReconstructionMaterial |
P59925
|
FINISHED |
| Object | Brick |
—
|
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: Brick | Statement: [Graff House, hasReconstructionMaterial, Brick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReconstructionMaterial Context triple: [Graff House, hasReconstructionMaterial, Brick]
-
A.
hasReconstructionWork
Indicates that an entity is undergoing, has undergone, or is associated with reconstruction or restoration work.
-
B.
haveReconstructionWork
Indicates that an entity is undergoing or is associated with reconstruction or restoration work.
-
C.
reconstructionUsedOriginalMaterials
Indicates that a reconstruction was carried out using the same physical materials as those of the original object or structure.
-
D.
hasReconstructionStandard
Indicates that something is associated with or governed by a specific standard or guideline for how it should be reconstructed.
-
E.
materialReusedAt
Indicates that some or all of a material is used again at a specified location or facility.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2557388190a2d15571bacd24f3 |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:25 p.m.