Triple
T31954540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firelands |
E815867
|
entity |
| Predicate | hasHistoricSociety |
P118524
|
FINISHED |
| Object | Firelands Historical Society |
—
|
NE NERFINISHED |
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: Firelands Historical Society | Statement: [Firelands, hasHistoricSociety, Firelands Historical Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSociety Context triple: [Firelands, hasHistoricSociety, Firelands Historical Society]
-
A.
historicalSociety
chosen
Indicates that an entity is a society or organization dedicated to preserving, studying, or promoting history.
-
B.
hasLocalHistoricalAssociations
Indicates that something is connected to historically significant events, people, or developments specific to a particular locality or region.
-
C.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
D.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
E.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: May 1, 2026, 12:08 a.m.