Triple
T7148535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle to Dr Arbuthnot |
E166630
|
entity |
| Predicate | addresseeNationality |
P59748
|
FINISHED |
| Object | Scottish |
—
|
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: Scottish | Statement: [Epistle to Dr Arbuthnot, addresseeNationality, Scottish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addresseeNationality Context triple: [Epistle to Dr Arbuthnot, addresseeNationality, Scottish]
-
A.
recipientNationality
chosen
Indicates that the recipient in a relationship or transaction has a specified national affiliation or citizenship.
-
B.
nationalityInText
Indicates that a person's nationality is mentioned or specified within a given text.
-
C.
bearerNationality
Indicates that one entity is the country or nationality associated with the bearer of another entity, such as a document or credential.
-
D.
creditorNationality
Indicates that the creditor is associated with, or belongs to, a particular nationality.
-
E.
debtorNationality
Indicates that the specified nationality is the country of citizenship or legal national affiliation of the debtor in the relationship.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d6313c8190bdd34e700fc65502 |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.