Triple
T3048813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vice-Chancellor |
E83517
|
entity |
| Predicate | termUsedIn |
P6238
|
FINISHED |
| Object | Commonwealth university systems |
—
|
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: Commonwealth university systems | Statement: [Vice-Chancellor, termUsedIn, Commonwealth university systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termUsedIn Context triple: [Vice-Chancellor, termUsedIn, Commonwealth university systems]
-
A.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
designationUsedFor
chosen
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
E.
isUsedUnder
Indicates that one entity is utilized or applied within the context, conditions, or framework defined by 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9baed3848190a8351d9c8c4edc79 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.