Triple
T4371908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rob Pike |
E98914
|
entity |
| Predicate | roleAtGoogle |
P13957
|
FINISHED |
| Object | Go team member |
—
|
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: Go team member | Statement: [Rob Pike, roleAtGoogle, Go team member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtGoogle Context triple: [Rob Pike, roleAtGoogle, Go team member]
-
A.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
C.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
D.
roleSimilarTo
Indicates that two entities have roles or functions that are alike or closely comparable in nature or responsibility.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521dffbc8190b9300a7f4f64bdc0 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.