Triple
T152599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Temple |
E3462
|
entity |
| Predicate | hasLibraryCollectionFocus |
P1843
|
FINISHED |
| Object | English law |
—
|
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: English law | Statement: [Inner Temple, hasLibraryCollectionFocus, English law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibraryCollectionFocus Context triple: [Inner Temple, hasLibraryCollectionFocus, English law]
-
A.
hasCollectionFocus
chosen
Indicates that something is primarily concerned with, centered on, or directed toward a particular collection or set of items.
-
B.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
C.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
D.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
-
E.
hasDigitalCollections
Indicates that an entity possesses or provides access to one or more collections of materials in digital form.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25810799c8190a515a39169126e46 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.