Triple
T20688343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Shih Chen |
E508480
|
entity |
| Predicate | startupRole |
P141061
|
FINISHED |
| Object | technical co-founder |
—
|
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: technical co-founder | Statement: [Steven Shih Chen, startupRole, technical co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startupRole Context triple: [Steven Shih Chen, startupRole, technical co-founder]
-
A.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
B.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
C.
launchPlatformRole
Indicates the functional role or responsibility an entity has in relation to a launch platform within a launch or deployment context.
-
D.
configurationRole
Indicates the role or function an entity assumes within a particular configuration or setup.
-
E.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10b7b808190bdb8b08e53168fb8 |
completed | April 21, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:49 a.m.