Triple
T178585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stat. |
E3631
|
entity |
| Predicate | hasCitationPattern |
P4468
|
FINISHED |
| Object | "[volume] Stat. [page]" |
—
|
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: "[volume] Stat. [page]" | Statement: [Stat., hasCitationPattern, "[volume] Stat. [page]"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitationPattern Context triple: [Stat., hasCitationPattern, "[volume] Stat. [page]"]
-
A.
citationStyle
chosen
Indicates the specific formatting and referencing conventions used to cite sources in a document or publication.
-
B.
hasSisterPublication
Indicates that one publication is related to another as a sister publication, typically under the same parent organization or closely associated in scope or branding.
-
C.
citation
Indicates that one entity references, quotes, or otherwise acknowledges another entity as a source of information or authority.
-
D.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
E.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fe7bb08190a56f4a54cadd2fef |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.