Triple
T7574076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerging Sources Citation Index |
E179318
|
entity |
| Predicate | indexingLevel |
P9799
|
FINISHED |
| Object | journal level |
—
|
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: journal level | Statement: [Emerging Sources Citation Index, indexingLevel, journal level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexingLevel Context triple: [Emerging Sources Citation Index, indexingLevel, journal level]
-
A.
indexLevelPublication
chosen
Indicates that a publication is associated with a specific index level (e.g., tier, rank, or category) within an indexing or classification system.
-
B.
indexType
Indicates the classification or category of an index associated with an entity or structure.
-
C.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
D.
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.
-
E.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
- 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f948e1e08190ad807292365a0c27 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:51 p.m.