Triple
T3940665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewing Kauffman |
E92024
|
entity |
| Predicate | positionInCompany |
P47952
|
FINISHED |
| Object | founder of Marion Laboratories |
—
|
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: founder of Marion Laboratories | Statement: [Ewing Kauffman, positionInCompany, founder of Marion Laboratories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCompany Context triple: [Ewing Kauffman, positionInCompany, founder of Marion Laboratories]
-
A.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
-
B.
positionInIndustry
Indicates the role, rank, or standing that an entity holds within a particular industry or sector.
-
C.
workPosition
chosen
Indicates the specific job role or position that an entity holds within an organization or workplace.
-
D.
rankWithinOrganization
Indicates the relative hierarchical position or level an entity holds within a specific organization.
-
E.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedfc88e4819084adefb695b975c5 |
completed | March 9, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.