Triple
T28180878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antelias |
E716021
|
entity |
| Predicate | hasLibraryOrArchive |
P123292
|
FINISHED |
| Object | archives of the Catholicosate of Cilicia |
—
|
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: archives of the Catholicosate of Cilicia | Statement: [Antelias, hasLibraryOrArchive, archives of the Catholicosate of Cilicia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibraryOrArchive Context triple: [Antelias, hasLibraryOrArchive, archives of the Catholicosate of Cilicia]
-
A.
hasLibraries
chosen
Indicates that an entity possesses, contains, or is associated with one or more libraries.
-
B.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
C.
hasOfficialLibrary
Indicates that an entity possesses or is served by a formally recognized, authorized library.
-
D.
isReferenceLibrary
Indicates that an entity functions as a reference library, i.e., a collection primarily intended for on-site consultation rather than lending.
-
E.
hasPublicLibraryType
Indicates that an entity is associated with a specific type or category of public library.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 27, 2026, 10:19 p.m.