Triple
T18255130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Ruan |
E437204
|
entity |
| Predicate | productTypeFounded |
P131043
|
FINISHED |
| Object | browser extension |
—
|
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: browser extension | Statement: [George Ruan, productTypeFounded, browser extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productTypeFounded Context triple: [George Ruan, productTypeFounded, browser extension]
-
A.
brandLaunchYear
Indicates the calendar year in which a brand was first introduced or launched to the market.
-
B.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
C.
coFoundedInYear
Indicates that two or more entities jointly founded something (such as an organization or company) in a specified year.
-
D.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
-
E.
brandFounded
Indicates that a specific brand was established or created at a particular point in time or by a particular founder or 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd84b3a481908bbc1a5e5034d397 |
completed | April 19, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:34 a.m.