Triple
T4124877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Tower |
E92699
|
entity |
| Predicate | financialIssue |
P24219
|
FINISHED |
| Object | loss of funding from J. P. Morgan |
—
|
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: loss of funding from J. P. Morgan | Statement: [Tesla Tower, financialIssue, loss of funding from J. P. Morgan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialIssue Context triple: [Tesla Tower, financialIssue, loss of funding from J. P. Morgan]
-
A.
fiscalIssue
chosen
Indicates a relationship where an entity is involved in, affected by, or associated with a financial or budgetary problem, concern, or matter.
-
B.
facingIssue
Indicates that an entity is currently experiencing, encountering, or dealing with a problem, difficulty, or obstacle.
-
C.
issuesCurrency
Indicates that an entity has the authority to create and put a specific currency into official circulation.
-
D.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
E.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.