Triple
T4504129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegro |
E101290
|
entity |
| Predicate | reducedBorderFormalities |
P56948
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Allegro, reducedBorderFormalities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducedBorderFormalities Context triple: [Allegro, reducedBorderFormalities, yes]
-
A.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
-
B.
hasLessStrictTradeControlsThan
Indicates that one entity’s trade regulations or restrictions are more relaxed or permissive compared to those of another entity.
-
C.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
D.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
E.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
- F. None of above. chosen
Provenance (4 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:01 p.m.