Triple
T9018659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Faculty Library |
E215657
|
entity |
| Predicate | providesFacility |
P12416
|
FINISHED |
| Object | reading rooms |
—
|
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: reading rooms | Statement: [Law Faculty Library, providesFacility, reading rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesFacility Context triple: [Law Faculty Library, providesFacility, reading rooms]
-
A.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
B.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
-
C.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
D.
basedOnFacility
Indicates that something is determined, derived, or decided according to the characteristics, rules, or conditions of a particular facility.
-
E.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a4085848190a6aa440e6307e93d |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.