Triple
T4138471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goodrich Castle |
E89213
|
entity |
| Predicate | builtOfStoneFrom |
P11047
|
FINISHED |
| Object | local sandstone quarries |
—
|
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 sandstone quarries | Statement: [Goodrich Castle, builtOfStoneFrom, local sandstone quarries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOfStoneFrom Context triple: [Goodrich Castle, builtOfStoneFrom, local sandstone quarries]
-
A.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
B.
builtFrom
chosen
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
C.
stoneFragmentsFrom
Indicates that one entity consists of or originates as stone fragments derived from another entity.
-
D.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
-
E.
foundationStoneLaid
Indicates that the initial, symbolic stone marking the start of constructing a building or structure has been formally placed.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.