Triple
T30633756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKB48 |
E779777
|
entity |
| Predicate | hasSisterGroup |
P3457
|
FINISHED |
| Object | SKE48 |
—
|
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: SKE48 | Statement: [AKB48, hasSisterGroup, SKE48]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterGroup Context triple: [AKB48, hasSisterGroup, SKE48]
-
A.
sisterGroup
Indicates that two groups share an immediate common ancestor in a hierarchy or classification, making them each other’s closest related group.
-
B.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
-
C.
hasSisterSubsystem
Indicates that one subsystem is related to another as a sister subsystem, meaning they share a common parent system or hierarchical level.
-
D.
hasSisterRelationshipType
Indicates that there exists a sister-type familial relationship between the related entities.
-
E.
hasSisterOrganization
chosen
Indicates that one organization is related to another as a sister organization, typically sharing a common parent, affiliation, or parallel status within the same overarching structure.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 8:28 p.m.