Triple
T26678213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacob Schueler |
E672523
|
entity |
| Predicate | roleAtCoors |
P164848
|
FINISHED |
| Object | original investor |
—
|
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: original investor | Statement: [Jacob Schueler, roleAtCoors, original investor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtCoors Context triple: [Jacob Schueler, roleAtCoors, original investor]
-
A.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
B.
roleAtA24
Indicates that an entity holds or held a specific role or position at the organization or project referred to as A24.
-
C.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
D.
roleAtHouston
Indicates that an entity holds or held a specific role or position at an organization, institution, or context associated with Houston.
-
E.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 27, 2026, 3:18 a.m.