Triple
T9102050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laudabiliter |
E218381
|
entity |
| Predicate | traditionallyCitedAs |
P68317
|
FINISHED |
| Object | authorization for English rule in Ireland |
—
|
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: authorization for English rule in Ireland | Statement: [Laudabiliter, traditionallyCitedAs, authorization for English rule in Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyCitedAs Context triple: [Laudabiliter, traditionallyCitedAs, authorization for English rule in Ireland]
-
A.
oftenCitedAs
Indicates that one entity is frequently referenced or mentioned as an example, source, or authority in relation to another entity.
-
B.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
C.
citationAs
chosen
Indicates that one entity is cited or referenced in the role or capacity specified by another entity (such as a particular work, version, or context).
-
D.
citationBy
Indicates that one work is cited or referenced by another work.
-
E.
citesAs
Indicates that one entity references or acknowledges another as a source of information, authority, or evidence.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc971435d08190b5007ed44ac0a364 |
completed | April 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.