Triple
T20399458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lytro |
E500291
|
entity |
| Predicate | totalFunding |
P75026
|
FINISHED |
| Object | over 200 million US dollars |
—
|
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: over 200 million US dollars | Statement: [Lytro, totalFunding, over 200 million US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalFunding Context triple: [Lytro, totalFunding, over 200 million US dollars]
-
A.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
approximateFundsRaised
chosen
Indicates an estimated amount of money that has been raised, rather than an exact or final total.
-
C.
fundingLevel
Indicates the amount or degree of financial resources allocated or committed to an entity, project, or activity.
-
D.
totalInvestment
Indicates the overall amount of resources (typically money) committed to a particular entity, project, or activity, aggregating all individual investments involved.
-
E.
fundedBy
Indicates that an entity receives financial support or resources from 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798cf04481909f183c4c75fe6d52 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.