Triple
T18878166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alice |
E461743
|
entity |
| Predicate | hasConventionalPartnerRole |
P133303
|
FINISHED |
| Object | Bob as receiver |
—
|
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: Bob as receiver | Statement: [Alice, hasConventionalPartnerRole, Bob as receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConventionalPartnerRole Context triple: [Alice, hasConventionalPartnerRole, Bob as receiver]
-
A.
hasPartnershipRole
Indicates that an entity holds a specific role or function within a partnership relationship with another entity.
-
B.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
hasExPartner
Indicates that one entity was formerly in a romantic or intimate partnership with another entity, but that relationship has ended.
-
D.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
-
E.
hasConsortRole
Indicates that an entity holds or is assigned the role or status of a consort in relation to another entity.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3cfc4408190a7ae91459f75be52 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e4978813d081908eaf25bb727fc6cf |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.