Triple
T1583701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web of Science |
E34023
|
entity |
| Predicate | indexingType |
P19875
|
FINISHED |
| Object | selective indexing |
—
|
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: selective indexing | Statement: [Web of Science, indexingType, selective indexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexingType Context triple: [Web of Science, indexingType, selective indexing]
-
A.
indexType
chosen
Indicates the classification or category of an index associated with an entity or structure.
-
B.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
C.
indexStructure
Indicates that one entity serves as an index or organizational framework that structures, arranges, or provides access to another entity or set of entities.
-
D.
indexProvider
Indicates that one entity serves as a provider or source of an index (such as a listing, catalog, or reference structure) that can be used by another entity.
-
E.
selectionIndexDefinition
Indicates the specific index or position used to select an item or element within an ordered collection or set.
- 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_69a885fceb2c8190b47e0f7c0aefbff0 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.