Triple
T33104840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Harrison |
E847156
|
entity |
| Predicate | presentDaySiteUse |
P16008
|
FINISHED |
| Object | commemorative and historical interpretation site |
—
|
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: commemorative and historical interpretation site | Statement: [Fort Harrison, presentDaySiteUse, commemorative and historical interpretation site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDaySiteUse Context triple: [Fort Harrison, presentDaySiteUse, commemorative and historical interpretation site]
-
A.
currentSiteUse
chosen
Indicates how a site is presently being used or the function it currently serves.
-
B.
presentDayAccess
Indicates that an entity currently has the ability or permission to access another entity or resource in the present day.
-
C.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
D.
primaryCurrentUse
Indicates the main way something is currently being used or its principal present function.
-
E.
presentDayIncludes
Indicates that the current day in a given calendar or time context encompasses or contains a specified time, date, or event.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:26 a.m.