Triple
T19421268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franekeradeel |
E485857
|
entity |
| Predicate | hadHistoricFunction |
P2715
|
FINISHED |
| Object | local government unit |
—
|
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: local government unit | Statement: [Franekeradeel, hadHistoricFunction, local government unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadHistoricFunction Context triple: [Franekeradeel, hadHistoricFunction, local government unit]
-
A.
historicalFunction
chosen
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
C.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
D.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
E.
isHistoric
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.