Triple
T32126954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Unit 2 |
E820526
|
entity |
| Predicate | hasSisterUnit |
P31639
|
FINISHED |
| Object | Salem Unit 1 |
—
|
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: Salem Unit 1 | Statement: [Salem Unit 2, hasSisterUnit, Salem Unit 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterUnit Context triple: [Salem Unit 2, hasSisterUnit, Salem Unit 1]
-
A.
hasSisterDistrict
Indicates that one district is designated as a sister district to another, typically reflecting a formal partnership or cooperative relationship between them.
-
B.
hasSisterSubsystem
Indicates that one subsystem is related to another as a sister subsystem, meaning they share a common parent system or hierarchical level.
-
C.
hasSisterOrganization
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.
-
D.
hasSister
chosen
Indicates that one entity is the sister of another entity.
-
E.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 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, 12:29 a.m.