Triple
T23046365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tools for Humanity |
E573886
|
entity |
| Predicate | raisedCapitalIn |
P134906
|
FINISHED |
| Object | Series A financing round |
—
|
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: Series A financing round | Statement: [Tools for Humanity, raisedCapitalIn, Series A financing round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisedCapitalIn Context triple: [Tools for Humanity, raisedCapitalIn, Series A financing round]
-
A.
raisedMoneyFor
Indicates that one entity collected or obtained funds specifically to support or benefit another entity, cause, or purpose.
-
B.
raisedVentureCapital
chosen
Indicates that an entity has obtained funding from venture capital investors.
-
C.
raisesCapitalFrom
Indicates that one entity obtains funding or financial resources from another entity.
-
D.
authorizedCapital
Indicates the legally approved maximum amount of share capital that a company is permitted to issue under its corporate charter or governing documents.
-
E.
madeCapital
Indicates that one entity was designated or established as the capital city of another entity (such as a country, state, or region).
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f185192754819093a87d23371e7bbc |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.