Triple
T14181454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | letters journal |
E351460
|
entity |
| Predicate | mayBeIndexedIn |
P108653
|
FINISHED |
| Object | scientific citation databases |
—
|
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: scientific citation databases | Statement: [letters journal, mayBeIndexedIn, scientific citation databases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeIndexedIn Context triple: [letters journal, mayBeIndexedIn, scientific citation databases]
-
A.
hasIndexing
Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
-
B.
usesIndexation
Indicates that one entity applies or relies on an indexing scheme or index-based method provided by or associated with another entity.
-
C.
isSearchable
Indicates that the referenced entity can be discovered or retrieved through a search operation or query.
-
D.
indexed
chosen
Indicates that one entity is organized, recorded, or referenced within a systematic index or catalog relative to another entity.
-
E.
isViewableIn
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61ca3ad88190944850c97760dcbf |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.