Triple
T23182871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cash App |
E579506
|
entity |
| Predicate | supportsInvestmentType |
P4851
|
FINISHED |
| Object | fractional shares |
—
|
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: fractional shares | Statement: [Cash App, supportsInvestmentType, fractional shares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInvestmentType Context triple: [Cash App, supportsInvestmentType, fractional shares]
-
A.
supportsVentureType
Indicates that an entity provides backing, resources, or compatibility for a specified type or category of venture.
-
B.
investmentType
chosen
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
C.
supportsTradingType
Indicates that one entity enables, allows, or is compatible with a specified type or mode of trading.
-
D.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
supportsCommodity
Indicates that one entity provides the necessary functionality, infrastructure, or compatibility for another entity to handle, use, or trade a specified commodity.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f705c14819082c8580a03ed6286 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.