Triple
T7909170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jarl |
E183653
|
entity |
| Predicate | historicalTitleRelation |
P28331
|
FINISHED |
| Object | jarl (Scandinavian noble title) |
—
|
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: jarl (Scandinavian noble title) | Statement: [Jarl, historicalTitleRelation, jarl (Scandinavian noble title)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTitleRelation Context triple: [Jarl, historicalTitleRelation, jarl (Scandinavian noble title)]
-
A.
titleRelation
chosen
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
B.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
C.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5c85ac81908de2ca387826ea2f |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.