Triple
T26965600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BGE [volume] [section] [page] |
E679163
|
entity |
| Predicate | citationElement |
P113948
|
FINISHED |
| Object | subject-matter section |
—
|
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: subject-matter section | Statement: [BGE [volume] [section] [page], citationElement, subject-matter section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citationElement Context triple: [BGE [volume] [section] [page], citationElement, subject-matter section]
-
A.
citationComponent
chosen
Indicates that one entity is a constituent part or segment of a larger citation associated with another entity.
-
B.
citationOf
Indicates that one entity cites, references, or formally acknowledges another entity as a source.
-
C.
citationAs
Indicates that one entity is cited or referenced in the role or capacity specified by another entity (such as a particular work, version, or context).
-
D.
citation
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
E.
citationRecord
Indicates that there exists a record documenting that one entity has cited or referenced 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6212035e881909a393a2411149481 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 6:35 a.m.