Triple
T23202563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | løgmaður |
E580357
|
entity |
| Predicate | isTraditionalTitle |
P11127
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [løgmaður, isTraditionalTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTraditionalTitle Context triple: [løgmaður, isTraditionalTitle, true]
-
A.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
B.
traditionalTitle
chosen
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
C.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
D.
usesTraditionalTitleSystem
Indicates that an entity follows or applies a customary, historically established system of formal titles or honorifics in its social or organizational structure.
-
E.
hasTraditionalName
Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907a8bb48190846802a24d33bccf |
completed | April 29, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:06 p.m.