Triple
T13528008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pro-vice-chancellors |
E323060
|
entity |
| Predicate | oftenHoldRank |
P7007
|
FINISHED |
| Object | professor |
—
|
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: professor | Statement: [pro-vice-chancellors, oftenHoldRank, professor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHoldRank Context triple: [pro-vice-chancellors, oftenHoldRank, professor]
-
A.
typicallyHoldsRank
chosen
Indicates that an entity is most commonly or usually associated with holding a particular rank or level in a hierarchy.
-
B.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
-
C.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
D.
oftenHeldToBe
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
E.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
- 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_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. |
Created at: April 9, 2026, 9:44 p.m.