Triple
T638060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Science Citation Index |
E16667
|
entity |
| Predicate | indexingUnit |
P6000
|
FINISHED |
| Object | journal |
—
|
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 | Statement: [Science Citation Index, indexingUnit, journal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexingUnit Context triple: [Science Citation Index, indexingUnit, journal]
-
A.
samplingUnit
Indicates that one entity serves as the basic unit or element from which samples are drawn or measured in a sampling process.
-
B.
indexingService
chosen
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
C.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
D.
componentUnit
Indicates that one entity functions as a constituent or sub-unit that forms part of a larger composite entity.
-
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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.