Triple
T2716702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drew Houston |
E59981
|
entity |
| Predicate | startupEcosystemRole |
P3571
|
FINISHED |
| Object | Silicon Valley entrepreneur |
—
|
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: Silicon Valley entrepreneur | Statement: [Drew Houston, startupEcosystemRole, Silicon Valley entrepreneur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startupEcosystemRole Context triple: [Drew Houston, startupEcosystemRole, Silicon Valley entrepreneur]
-
A.
roleInEcosystem
chosen
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
B.
technologyRole
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
C.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
D.
typeOfEntrepreneur
Indicates the specific category or kind of entrepreneur that an entity is classified as.
-
E.
infrastructureRole
Indicates that one entity serves a specific infrastructural function or capacity in relation to 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda964d4881908179b2a1b16411e4 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.