Triple
T13527992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pro-vice-chancellors |
E323060
|
entity |
| Predicate | typicallyFoundIn |
P33560
|
FINISHED |
| Object | universities |
—
|
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: universities | Statement: [pro-vice-chancellors, typicallyFoundIn, universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyFoundIn Context triple: [pro-vice-chancellors, typicallyFoundIn, universities]
-
A.
commonlyFoundOn
chosen
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
foundInRegion
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
E.
isTypicallyServedIn
Indicates that something (such as a food or drink) is most commonly or customarily presented or contained within a particular type of vessel or container.
- 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.