Triple
T11751333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EconLit |
E279410
|
entity |
| Predicate | hasCitationInformation |
P101148
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EconLit, hasCitationInformation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitationInformation Context triple: [EconLit, hasCitationInformation, yes]
-
A.
hasCitationForm
Indicates that an entity is associated with a specific standardized form used for citing or referencing it.
-
B.
hasFullCitation
Indicates that an entity is associated with a complete and properly formatted bibliographic reference.
-
C.
hasCitationCount
Indicates that an entity (such as a publication) is associated with a specific number representing how many times it has been cited.
-
D.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by another entity.
-
E.
hasCitationImpact
Indicates that one entity (such as a publication, author, or venue) exerts measurable influence on scholarly work through citations it receives or generates.
- F. None of above. chosen
Provenance (4 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a509c2448190b0deb7ed29c3a73f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d890458d948190b15054c9ba0fd923 |
completed | April 10, 2026, 5:53 a.m. |
Created at: April 8, 2026, 9:41 p.m.