Triple
T30633761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKB48 |
E779777
|
entity |
| Predicate | hasOverseasSisterGroup |
P3457
|
FINISHED |
| Object | JKT48 |
—
|
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: JKT48 | Statement: [AKB48, hasOverseasSisterGroup, JKT48]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverseasSisterGroup Context triple: [AKB48, hasOverseasSisterGroup, JKT48]
-
A.
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.
-
B.
hasNumberOfSisterOrganizations
Indicates the count of sister or peer organizations associated with a given organization.
-
C.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
D.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
-
E.
hasSisterDistrict
Indicates that one district is designated as a sister district to another, typically reflecting a formal partnership or cooperative relationship between them.
- 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_69f68a4ef69881909434a14b0f43e6bf |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.