Triple
T20141190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player 218 |
E491167
|
entity |
| Predicate | financialStatusInStory |
P104562
|
FINISHED |
| Object | heavily in debt |
—
|
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: heavily in debt | Statement: [Player 218, financialStatusInStory, heavily in debt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialStatusInStory Context triple: [Player 218, financialStatusInStory, heavily in debt]
-
A.
hasFinancialStatus
chosen
Indicates that an entity possesses or is characterized by a particular financial condition, standing, or level of economic well-being.
-
B.
relationshipStatusInStory
Indicates the type or state of the relationship between entities as it exists within the context of a specific story or narrative.
-
C.
monetaryStatus
Indicates the financial condition or situation of an entity, such as its wealth, solvency, or level of monetary resources.
-
D.
netWorthStatus
Indicates the financial standing or wealth level of an entity relative to defined net worth categories or thresholds.
-
E.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679b179c8190a9511df8ed82098a |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:32 p.m.