Triple
T38288143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl Marischal |
E1022277
|
entity |
| Predicate | officeLinkedToTitle |
P5175
|
FINISHED |
| Object | Marischal 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: Marischal of Scotland | Statement: [Earl Marischal, officeLinkedToTitle, Marischal of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeLinkedToTitle Context triple: [Earl Marischal, officeLinkedToTitle, Marischal of Scotland]
-
A.
workTitleRelation
Indicates a relationship where one entity is the title or name of a work (such as a book, film, or artwork) associated with another entity.
-
B.
associatedTitle
chosen
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
-
C.
relatesToOffice
Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
-
D.
associatedTitleType
Indicates the type or category of a title that is linked or related to another entity or primary title.
-
E.
officeSymbolizes
Indicates that an office represents, embodies, or stands as a symbol for a particular concept, status, authority, or organizational role.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00717f539c8190b70dd0e72c6f7d24 |
completed | May 10, 2026, 11:52 a.m. |
| PD | Predicate disambiguation | batch_6a00710278fc81908889afdcf459ff01 |
completed | May 10, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:30 p.m.