Triple
T6419161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tain |
E127900
|
entity |
| Predicate | hasHistoricCharter |
P8747
|
FINISHED |
| Object | medieval royal charter |
—
|
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: medieval royal charter | Statement: [Tain, hasHistoricCharter, medieval royal charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricCharter Context triple: [Tain, hasHistoricCharter, medieval royal charter]
-
A.
hasRoyalCharter
Indicates that an entity has been formally granted a royal charter by a monarch or royal authority.
-
B.
hasCharter
chosen
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
C.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
-
D.
charterDate
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
E.
hasCharterStatus
Indicates that an entity possesses a specific charter designation or status granted by an authoritative body.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690194dc8190b3382bd5f92876b5 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.