Triple
T3578923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Point National Historic Site |
E75753
|
entity |
| Predicate | hasConstructionEndDate |
P23965
|
FINISHED |
| Object | 1861 |
—
|
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: 1861 | Statement: [Fort Point National Historic Site, hasConstructionEndDate, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionEndDate Context triple: [Fort Point National Historic Site, hasConstructionEndDate, 1861]
-
A.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
B.
constructionCompletedUnder
Indicates that the completion of a construction project occurred under the responsibility, authority, or supervision of a specified agent, organization, or governing body.
-
C.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
reconstructionEndDate
Indicates the date on which a reconstruction process or project is completed.
-
E.
constructionDate
chosen
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0defe14819095a337a840e33300 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.