Triple
T37882364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack FM |
E944899
|
entity |
| Predicate | sisterFormatOf |
P189569
|
FINISHED |
| Object | Bob FM |
—
|
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: Bob FM | Statement: [Jack FM, sisterFormatOf, Bob FM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sisterFormatOf Context triple: [Jack FM, sisterFormatOf, Bob FM]
-
A.
hasSisterPublication
Indicates that one publication is related to another as a sister publication, typically under the same parent organization or closely associated in scope or branding.
-
B.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
C.
sisterSegment
Indicates that two segments share a common parent or grouping and are considered parallel or equivalent parts within that larger structure.
-
D.
sisterWork
Indicates that one entity works at the same workplace as another entity’s sister.
-
E.
sisterGroup
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.