Triple
T11961564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal of Political Economy |
E284679
|
entity |
| Predicate | hasBackIssues |
P102511
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Journal of Political Economy, hasBackIssues, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackIssues Context triple: [Journal of Political Economy, hasBackIssues, true]
-
A.
hadIssue
Indicates that an entity experienced, encountered, or was affected by a particular problem, defect, or difficulty.
-
B.
hasHistoryOf
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
C.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
D.
hasPracticeIssue
Indicates that an entity is associated with a specific problem, concern, or challenge arising in practical or real-world practice.
-
E.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.