Triple
T37760710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. E. Vedrenne |
E941258
|
entity |
| Predicate | hasNotablePartnerInWork |
P88250
|
FINISHED |
| Object | George Bernard Shaw |
E52265
|
NE 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: George Bernard Shaw | Statement: [J. E. Vedrenne, hasNotablePartnerInWork, George Bernard Shaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePartnerInWork Context triple: [J. E. Vedrenne, hasNotablePartnerInWork, George Bernard Shaw]
-
A.
hasPartnerInWork
chosen
Indicates that one entity collaborates professionally or is partnered with another entity in a work-related context.
-
B.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
D.
hasPartnershipRole
Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
-
E.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
- F. None of above.
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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40f178dea4819092ef0f7be9da3f30 |
completed | June 28, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.