Triple
T16421002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Library |
E398816
|
entity |
| Predicate | isReferenceLibrary |
P123364
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [London Library, isReferenceLibrary, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReferenceLibrary Context triple: [London Library, isReferenceLibrary, false]
-
A.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
B.
usedInLibrary
Indicates that something is utilized or applied within the context of a library, such as a software library or a physical library system.
-
C.
isReferenceOnly
Indicates that the associated item is intended solely for reference purposes and not for direct use, modification, or primary operation.
-
D.
hasOfficialLibrary
Indicates that an entity possesses or is served by a formally recognized, authorized library.
-
E.
implementedInLibrary
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328f735b08190aec8331f54817462 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.