Triple
T33630278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jill |
E861533
|
entity |
| Predicate | memberOfDuoWith |
P81362
|
FINISHED |
| Object | Jack |
—
|
NE NERFINISHED |
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: Jack | Statement: [Jill, memberOfDuoWith, Jack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberOfDuoWith Context triple: [Jill, memberOfDuoWith, Jack]
-
A.
memberOfGroupWith
Indicates that an entity belongs to, or is associated as a member with, a particular group or collection of entities.
-
B.
associatedWithDuo
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
-
C.
duoMember
chosen
Indicates that an entity is one of the two participants forming a duo with another entity.
-
D.
includedMembersOf
Indicates that certain members or elements are contained within, or form part of, a specified group or collection.
-
E.
killsMembersOf
Indicates that one entity causes the death of individuals who belong to a particular group or organization.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:41 a.m.