Triple
T11955276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romania and Ukraine |
E284535
|
entity |
| Predicate | areNeighborsSince |
P57960
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [Romania and Ukraine, areNeighborsSince, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areNeighborsSince Context triple: [Romania and Ukraine, areNeighborsSince, 1991]
-
A.
haveSharedBorderSince
chosen
Indicates that two entities have had a common boundary or border continuously from a specified point in time onward.
-
B.
hasNeighborRelationshipWith
Indicates that one entity is located adjacent to or directly next to another entity, sharing a neighbor relationship.
-
C.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
D.
isNeighboringTimeZoneTo
Indicates that two time zones are directly adjacent to each other, typically sharing a common boundary or differing by one standard time offset step.
-
E.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.