Triple
T7801606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arts and Humanities Citation Index |
E180445
|
entity |
| Predicate | indexingMethod |
P34125
|
FINISHED |
| Object | citation 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: citation indexing | Statement: [Arts and Humanities Citation Index, indexingMethod, citation indexing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexingMethod Context triple: [Arts and Humanities Citation Index, indexingMethod, citation indexing]
-
A.
indexMethod
chosen
Indicates the method or technique used to create, organize, or access an index for a given resource or dataset.
-
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.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
D.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
E.
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.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.