Triple
T15255032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew W. Houston |
E364622
|
entity |
| Predicate | hasRoleAtOrganization |
P12630
|
FINISHED |
| Object | CEO at Dropbox |
—
|
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: CEO at Dropbox | Statement: [Andrew W. Houston, hasRoleAtOrganization, CEO at Dropbox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleAtOrganization Context triple: [Andrew W. Houston, hasRoleAtOrganization, CEO at Dropbox]
-
A.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
hasPositionInOrganization
chosen
Indicates that an entity holds a specific role, job, or position within a particular organization.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
hasNameInOrganization
Indicates that an entity is known by a particular name within the context of a specific organization.
-
E.
hasOrganLevelOrganization
Indicates that an entity possesses a level of biological organization in which distinct organs are present and functionally integrated.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f8cb308190933c4478aa096e24 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.