Triple
T27890703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAR Library |
E705345
|
entity |
| Predicate | hasIndexes |
P193880
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [DAR Library, hasIndexes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndexes Context triple: [DAR Library, hasIndexes, yes]
-
A.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
B.
hasIndexSet
Indicates that something is associated with, defined over, or organized according to a particular set of indices.
-
C.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
D.
hasIndexer
Indicates that one entity serves as an indexer (e.g., for searching, cataloging, or organizing) for another entity.
-
E.
hasIndexProvider
Indicates that an entity is associated with or uses a specific index provider responsible for supplying indexing capabilities or services.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
| PDg | Predicate description generation | batch_69fd592cc56081908ce456114d407616 |
completed | May 8, 2026, 3:31 a.m. |
Created at: April 27, 2026, 6:35 p.m.