Triple
T27734192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CollectionBase |
E697493
|
entity |
| Predicate | hasIndexer |
P193348
|
FINISHED |
| Object | Item[Int32] |
—
|
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: Item[Int32] | Statement: [CollectionBase, hasIndexer, Item[Int32]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndexer Context triple: [CollectionBase, hasIndexer, Item[Int32]]
-
A.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
B.
hasIndexProvider
Indicates that an entity is associated with or uses a specific index provider responsible for supplying indexing capabilities or services.
-
C.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
D.
isIndexedFor
Indicates that something has been organized or recorded in an index so it can be efficiently located, searched, or retrieved.
-
E.
hasIndexSet
Indicates that something is associated with, defined over, or organized according to a particular set of indices.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 27, 2026, 3:12 p.m.