Triple
T9431816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expa |
E227394
|
entity |
| Predicate | hasFounderBackgroundIn |
P34789
|
FINISHED |
| Object | technology entrepreneurship |
—
|
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: technology entrepreneurship | Statement: [Expa, hasFounderBackgroundIn, technology entrepreneurship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderBackgroundIn Context triple: [Expa, hasFounderBackgroundIn, technology entrepreneurship]
-
A.
hasFounderBackground
chosen
Indicates that an entity has a founder whose background (such as experience, education, or prior roles) matches a specified profile or characteristic.
-
B.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
C.
hasAuthorBackgroundIn
Indicates that an author possesses a particular background, such as education, experience, or expertise, in a specified field or domain.
-
D.
hasTypicalFounder
Indicates that an entity is commonly or characteristically founded or established by a particular type of founder.
-
E.
hasParentCompanyFounder
Indicates that an entity is the founder of the parent company of 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.