Triple
T38102941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Glace_Bay |
E951433
|
entity |
| Predicate | hasHistoricalRules |
P12106
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [America/Glace_Bay, hasHistoricalRules, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalRules Context triple: [America/Glace_Bay, hasHistoricalRules, true]
-
A.
hasRegulationHistory
Indicates that there exists a record or sequence of regulatory actions, decisions, or statuses associated with the entity over time.
-
B.
hasReplayRuleHistorically
chosen
Indicates that a replay rule applied to an entity at some point in the past, regardless of whether it is still in effect now.
-
C.
historicalStateRule
Indicates that one state historically governed, controlled, or exercised formal rule over another entity during a past period.
-
D.
hasHistoricalDetail
Indicates that something includes or is associated with specific information about past events, contexts, or developments.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:21 p.m.