Triple
T7393799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Reilly AlphaTech Ventures |
E170570
|
entity |
| Predicate | typicalInvestorRole |
P66571
|
FINISHED |
| Object | lead investor in early rounds |
—
|
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: lead investor in early rounds | Statement: [O'Reilly AlphaTech Ventures, typicalInvestorRole, lead investor in early rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInvestorRole Context triple: [O'Reilly AlphaTech Ventures, typicalInvestorRole, lead investor in early rounds]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typeOfInvestor
Indicates the kind or category of investor that a given entity is classified as.
-
C.
roleInFinance
chosen
Indicates that an entity holds a specific function, responsibility, or position within a financial context, system, or transaction.
-
D.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
E.
vestmentStyle
Indicates the style or type of clothing or ceremonial garments associated with an 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2263b48819089319a2a2f0d3357 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.