Triple
T6056446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linacre College, Oxford |
E134922
|
entity |
| Predicate | prioritises |
P68004
|
FINISHED |
| Object | environmental responsibility |
—
|
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: environmental responsibility | Statement: [Linacre College, Oxford, prioritises, environmental responsibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prioritises Context triple: [Linacre College, Oxford, prioritises, environmental responsibility]
-
A.
planningPriority
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
B.
limitsPriorityOf
Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
-
C.
supportsPriority
Indicates that one entity provides functionality or capability for handling or honoring priority levels associated with another entity or operation.
-
D.
managementPriority
Indicates the relative level of importance or urgency assigned to managing or addressing a particular entity, issue, or task.
-
E.
missionPriority
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
- 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570bf01c8190a8b2c25b7805d403 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:09 p.m.