Triple
T35115685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bildad |
E1013427
|
entity |
| Predicate | relationshipToJob |
P110367
|
FINISHED |
| Object | dialogue partner |
—
|
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: dialogue partner | Statement: [Bildad, relationshipToJob, dialogue partner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToJob Context triple: [Bildad, relationshipToJob, dialogue partner]
-
A.
employerRelationship
Indicates a relationship in which one entity acts as the employer of another, having authority to hire, direct, and compensate the other party for work performed.
-
B.
hasRelationshipToWork
chosen
Indicates a relationship where an entity has a specific connection, role, or association with a particular work or piece of work.
-
C.
relationshipToOrganization
Indicates the nature or type of connection an entity has with a specific organization, such as affiliation, membership, or role.
-
D.
workTitleRelation
Indicates a relationship where one entity is the title or name of a work (such as a book, film, or artwork) associated with another entity.
-
E.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
- 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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.