Triple
T17208132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greta Tugendhat |
E417653
|
entity |
| Predicate | coCommissionedWith |
P68728
|
FINISHED |
| Object | her husband |
—
|
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: her husband | Statement: [Greta Tugendhat, coCommissionedWith, her husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coCommissionedWith Context triple: [Greta Tugendhat, coCommissionedWith, her husband]
-
A.
commissionedWith
chosen
Indicates that one entity was created, produced, or initiated as part of the same commissioning event or request as another entity.
-
B.
commissionedBy
Indicates that one entity has been formally requested, authorized, or hired by another entity to create, perform, or carry out something.
-
C.
commissioned
Indicates that one entity formally authorized or ordered another entity to create, produce, or carry out something, often in exchange for payment or obligation.
-
D.
commissionedFor
Indicates that something was formally requested or created to serve a specific purpose, project, or recipient.
-
E.
commissionedIn
Indicates that an entity was formally requested or authorized to be created, produced, or carried out in a specific time period or location.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc283648190b2c1f957940024aa |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.