Triple
T431901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Normandy |
E9730
|
entity |
| Predicate | titleHolderRole |
P7034
|
FINISHED |
| Object | head of state of Jersey |
—
|
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: head of state of Jersey | Statement: [Duke of Normandy, titleHolderRole, head of state of Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderRole Context triple: [Duke of Normandy, titleHolderRole, head of state of Jersey]
-
A.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
B.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
C.
titleHeldIn
chosen
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
-
D.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
E.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eef07e748190b05392778f3de980 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.