Triple
T27477306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peirce-Nichols House |
E693497
|
entity |
| Predicate | significantRebuildDate |
P13795
|
FINISHED |
| Object | 1801 |
—
|
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: 1801 | Statement: [Peirce-Nichols House, significantRebuildDate, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantRebuildDate Context triple: [Peirce-Nichols House, significantRebuildDate, 1801]
-
A.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
B.
hasRebuiltDate
chosen
Indicates the date on which something was rebuilt or reconstructed.
-
C.
reconstructionBuiltAt
Indicates that a reconstruction of something was built or carried out at a specific location or site.
-
D.
rebuiltOrModifiedDuring
Indicates that an existing entity was reconstructed, renovated, or otherwise significantly altered during a specified time period or event.
-
E.
rebuiltBetween
Indicates that an entity was reconstructed or rebuilt during a time interval bounded by two specified temporal points.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 12:57 p.m.