Triple
T15011100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shark Tank |
E377836
|
entity |
| Predicate | typicalDealStructure |
P32903
|
FINISHED |
| Object | equity investment |
—
|
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: equity investment | Statement: [Shark Tank, typicalDealStructure, equity investment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDealStructure Context triple: [Shark Tank, typicalDealStructure, equity investment]
-
A.
dealStructure
chosen
Indicates how the terms, components, and conditions of a transaction or agreement are organized and related to one another.
-
B.
typeOfDeal
Indicates the specific category or nature of a deal or agreement that applies between entities.
-
C.
loanStructure
Indicates the specific terms, components, and repayment arrangement that define how a loan is organized between parties.
-
D.
dealContent
Indicates that one entity contains, specifies, or represents the substantive terms, details, or material of a deal or agreement involving another entity.
-
E.
typicalLotType
Indicates that one entity is the standard or commonly occurring type of lot associated with another entity.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded734943481908dad4ceed4fe850c |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.