Triple
T8060419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D. Richard Hipp |
E188104
|
entity |
| Predicate | organizationFoundedType |
P8556
|
FINISHED |
| Object | software consulting company |
—
|
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: software consulting company | Statement: [D. Richard Hipp, organizationFoundedType, software consulting company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationFoundedType Context triple: [D. Richard Hipp, organizationFoundedType, software consulting company]
-
A.
foundedOrganizationType
Indicates that an entity established or created an organization of a specified type (e.g., company, nonprofit, institution).
-
B.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
-
C.
foundedOrganization
Indicates that an entity established or created an organization.
-
D.
organizationTypeFounded
chosen
Indicates the type or category of organization that was established or created in a founding event.
-
E.
foundingOrganization
Indicates the organization that established or created another entity, such as a company, institution, or project.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcc61c0819085edc26e75c5f6d5 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.