Triple
T25499982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansingburgh |
E639081
|
entity |
| Predicate | hasNotablePeriodOfConstruction |
P22153
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Lansingburgh, hasNotablePeriodOfConstruction, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePeriodOfConstruction Context triple: [Lansingburgh, hasNotablePeriodOfConstruction, 19th century]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
hasMonumentInPeriod
Indicates that a monument is associated with or existed during a specified time period.
-
C.
originallyErectedIn
Indicates that something was first constructed or put up in a specific place or location.
-
D.
hasBuildingPeriod
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
E.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 21, 2026, 2:42 p.m.