Triple
T35379626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepridruženi poslanci |
E1022608
|
entity |
| Predicate | mayDifferBy |
P53790
|
FINISHED |
| Object | speaking rights between institutions |
—
|
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: speaking rights between institutions | Statement: [Nepridruženi poslanci, mayDifferBy, speaking rights between institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDifferBy Context triple: [Nepridruženi poslanci, mayDifferBy, speaking rights between institutions]
-
A.
mayDifferFrom
chosen
Indicates that one entity is allowed or expected to be different from another entity, without requiring them to be identical.
-
B.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
C.
isDifferenceOf
Indicates that one quantity or entity represents the result obtained by subtracting one specified quantity or entity from another.
-
D.
mayBeEqualTo
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
E.
differsInLengthFrom
Indicates that the length or duration of one entity is not equal to that of another entity.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.