Triple
T26221216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–German Parliamentary Assembly |
E655767
|
entity |
| Predicate | hasBilateralCharacter |
P88544
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Polish–German Parliamentary Assembly, hasBilateralCharacter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBilateralCharacter Context triple: [Polish–German Parliamentary Assembly, hasBilateralCharacter, true]
-
A.
isBilateral
chosen
Indicates that the relationship or interaction involves two sides, parties, or entities mutually.
-
B.
hasTwinCharacters
Indicates that two characters are twins, sharing the same parents and birth time or very close birth times.
-
C.
typicalBilateralEquivalent
Indicates that two entities are considered standard or typical counterparts to each other in a bilateral relationship or comparison.
-
D.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
-
E.
hasBilateralChamberSupport
Indicates that an entity receives formal backing or endorsement from both chambers of a bicameral legislative body.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 8:56 p.m.