Triple
T8825320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Post-Keynesian economics |
E210000
|
entity |
| Predicate | viewsFirmsAs |
P84833
|
FINISHED |
| Object | oligopolistic |
—
|
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: oligopolistic | Statement: [Post-Keynesian economics, viewsFirmsAs, oligopolistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsFirmsAs Context triple: [Post-Keynesian economics, viewsFirmsAs, oligopolistic]
-
A.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
-
B.
lawFirm
Indicates a relationship where one entity is a law firm that provides legal services or representation to another entity.
-
C.
viewsMarketAs
Indicates that one entity regards or interprets another entity as a market or commercial opportunity.
-
D.
viewsLawAs
Indicates that one entity regards, interprets, or conceptualizes the law in a particular way or from a particular perspective.
-
E.
architectureFirm
Indicates that one entity is an architecture firm responsible for providing architectural services or design work to another entity.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc60332d208190972a8b03fbd760ee |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:46 p.m.