Triple
T34722095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Knoop |
E1000943
|
entity |
| Predicate | companyFoundedAt |
P193273
|
FINISHED |
| Object | Columbia, Missouri (Zapier) |
—
|
NE NERFINISHED |
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: Columbia, Missouri (Zapier) | Statement: [Mike Knoop, companyFoundedAt, Columbia, Missouri (Zapier)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyFoundedAt Context triple: [Mike Knoop, companyFoundedAt, Columbia, Missouri (Zapier)]
-
A.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
B.
companyFoundedWith
Indicates that a company was established using or in association with a particular resource, organization, or founding context.
-
C.
organizationFoundedAs
Indicates that an organization was originally established under a particular name, form, or predecessor entity.
-
D.
coFoundedInYear
Indicates that two or more entities jointly founded something (such as an organization or company) in a specified year.
-
E.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
- 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_69f76daeb6e48190a4c9a6b0edc80f72 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
| PDg | Predicate description generation | batch_69fd3d45ccb8819082f15e60bd33afc9 |
completed | May 8, 2026, 1:32 a.m. |
Created at: May 3, 2026, 3:59 p.m.