Triple
T13528015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pro-vice-chancellors |
E323060
|
entity |
| Predicate | haveAlternativeTitle |
P110696
|
FINISHED |
| Object | pro vice-chancellor |
—
|
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: pro vice-chancellor | Statement: [pro-vice-chancellors, haveAlternativeTitle, pro vice-chancellor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveAlternativeTitle Context triple: [pro-vice-chancellors, haveAlternativeTitle, pro vice-chancellor]
-
A.
hasAlternativeEditionTitle
Indicates that an entity has a different or variant title used in another edition of the same work.
-
B.
hasTitleHolderAlternativeName
Indicates that an entity serving as a title holder is known by an alternative or additional name.
-
C.
alternateWorkingTitle
Indicates that one title serves as an alternative working title for the same work or project as another title.
-
D.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
E.
filmAlternateTitle
Indicates that a film is known or released under an alternative title.
- F. None of above. chosen
Provenance (4 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafb8e0cc8190b47f6aeb8ced470e |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.