Triple
T38159690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Edinburgh |
E952984
|
entity |
| Predicate | foundingCharterBy |
P17068
|
FINISHED |
| Object | James VI of Scotland |
—
|
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: James VI of Scotland | Statement: [University of Edinburgh, foundingCharterBy, James VI of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingCharterBy Context triple: [University of Edinburgh, foundingCharterBy, James VI of Scotland]
-
A.
foundedByCharterFrom
chosen
Indicates that an entity was formally established through an official charter issued by another entity.
-
B.
governedByCharterFrom
Indicates that an entity operates under the authority, rules, or framework established by a specific charter issued by another entity.
-
C.
charterDefines
Indicates that a charter specifies or establishes the rules, roles, or scope governing something.
-
D.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
E.
foundingDocument
Indicates that one entity serves as the official charter, constitution, or primary legal/organizational document that establishes or defines the other entity.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4:21 p.m.