Triple
T29019374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Pavia |
E737408
|
entity |
| Predicate | historicallyPrecededTitleOf |
P2939
|
FINISHED |
| Object | Duke of Milan |
—
|
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: Duke of Milan | Statement: [Count of Pavia, historicallyPrecededTitleOf, Duke of Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPrecededTitleOf Context triple: [Count of Pavia, historicallyPrecededTitleOf, Duke of Milan]
-
A.
predecessorTitleHolder
Indicates that one entity previously held a particular title or position before another entity.
-
B.
predecessorTitleContext
Indicates that the relationship specifies the contextual circumstances (such as role, period, or setting) under which a predecessor’s title is relevant or applies.
-
C.
isHistoricTitle
Indicates that a given title or designation was used in the past and is no longer current, but is retained for historical reference.
-
D.
previousTitle
chosen
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
E.
earlyTitleOf
Indicates that one entity served as an earlier or preliminary title for another 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 28, 2026, 9:48 a.m.