Triple
T10516707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haworth Parsonage |
E248052
|
entity |
| Predicate | rebuiltOrExtended |
P61916
|
FINISHED |
| Object | 1802 |
—
|
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: 1802 | Statement: [Haworth Parsonage, rebuiltOrExtended, 1802]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuiltOrExtended Context triple: [Haworth Parsonage, rebuiltOrExtended, 1802]
-
A.
rebuiltOrExpanded
chosen
Indicates that one entity has been reconstructed, enlarged, or otherwise significantly developed from its previous form or state.
-
B.
rebuiltFor
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
-
C.
rebuiltUnder
Indicates that an entity was reconstructed or restored while being subject to the authority, control, or governance of another entity.
-
D.
largelyRebuilt
Indicates that an entity has been substantially reconstructed or renovated, with most of its original structure replaced or significantly altered.
-
E.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cc58b081908ef15aa89b396db6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.