Triple
T4021325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Scholar |
E91284
|
entity |
| Predicate | supportsCitationFormats |
P30925
|
FINISHED |
| Object | BibTeX |
—
|
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: BibTeX | Statement: [Google Scholar, supportsCitationFormats, BibTeX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCitationFormats Context triple: [Google Scholar, supportsCitationFormats, BibTeX]
-
A.
citationFormatIncludes
Indicates that a particular citation format specification contains or incorporates a given element, rule, or component as part of its structure.
-
B.
hasCitationForm
chosen
Indicates that an entity is associated with a specific standardized form used for citing or referencing it.
-
C.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by another entity.
-
D.
usesCitation
Indicates that one entity supports or references its content by citing another entity as a source.
-
E.
hasFullCitation
Indicates that an entity is associated with a complete and properly formatted bibliographic reference.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.