Triple
T22198275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bull |
E548603
|
entity |
| Predicate | basedOnOccupationOf |
P71047
|
FINISHED |
| Object | trial consultant |
—
|
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: trial consultant | Statement: [Bull, basedOnOccupationOf, trial consultant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnOccupationOf Context triple: [Bull, basedOnOccupationOf, trial consultant]
-
A.
basedOnCareerOf
Indicates that something (such as a work, character, or storyline) is derived from, inspired by, or modeled on the career or professional life of a particular person.
-
B.
basedOnProfession
chosen
Indicates that the relationship or action is determined or derived from a person’s profession or occupational role.
-
C.
usedByOccupation
Indicates that something (such as a tool, method, or resource) is utilized in the performance of a particular occupation or job.
-
D.
ledByOccupation
Indicates that an entity is directed or governed by someone holding a specific occupation or professional role.
-
E.
basedOnWorkTitle
Indicates that something is derived from, adapted from, or otherwise created based on a work identified by its title.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae8c74c819080c7f9e8383ecaa7 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.