Triple
T27509958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strand Campus, King’s College London |
E694380
|
entity |
| Predicate | hostsLibrary |
P3556
|
FINISHED |
| Object | Maughan Library |
—
|
NE NERFINISHED |
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: Maughan Library | Statement: [Strand Campus, King’s College London, hostsLibrary, Maughan Library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsLibrary Context triple: [Strand Campus, King’s College London, hostsLibrary, Maughan Library]
-
A.
hostsResource
Indicates that one entity provides the environment or infrastructure in which another entity (the resource) resides, is stored, or is made available.
-
B.
hostsUnit
chosen
Indicates that one entity serves as the location or container in which another unit is situated, operates, or is organized.
-
C.
hostsBuilding
Indicates that one entity serves as the location or site that accommodates or contains a particular building.
-
D.
hostsPartOf
Indicates that one entity serves as the hosting environment or container for a specific part or component of another entity.
-
E.
hostStructure
Indicates that one structure serves as the host or containing framework for another structure.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 1:15 p.m.