Triple
T8983706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom Hofmann |
E214598
|
entity |
| Predicate | VineRole |
P61078
|
FINISHED |
| Object | co-founder |
—
|
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: co-founder | Statement: [Dom Hofmann, VineRole, co-founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VineRole Context triple: [Dom Hofmann, VineRole, co-founder]
-
A.
roleAtVine
chosen
Indicates that an entity holds or held a specific role or position at the company Vine.
-
B.
typicalVineTraining
Indicates that one entity is the standard or commonly used method of training or shaping the growth of another entity, typically in a vine or climbing context.
-
C.
viticulturalRole
Indicates the specific function, responsibility, or involvement an entity has within viticulture or grape-growing activities.
-
D.
neighboringVineyard
Indicates that one vineyard is located adjacent to or very close to another vineyard.
-
E.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67eb3cfc8190900a8253cc44621c |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:03 p.m.