Triple
T30905130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battery Park National Register Historic District |
E787277
|
entity |
| Predicate | hasBuiltDuringPeriod |
P53662
|
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: [Battery Park National Register Historic District, hasBuiltDuringPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuiltDuringPeriod Context triple: [Battery Park National Register Historic District, hasBuiltDuringPeriod, 19th century]
-
A.
hasBuildingPeriod
chosen
Indicates that a building or structure is associated with a specific time period during which it was constructed or significantly developed.
-
B.
hasBuilt
Indicates that one entity is the creator or constructor of another entity.
-
C.
appliedDuringPeriod
Indicates that an action, condition, or status was in effect throughout a specified time period.
-
D.
acquiredInPeriod
Indicates that one entity was acquired by another within a specified time period.
-
E.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:50 p.m.