Triple
T30063349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavaria and Styria |
E763957
|
entity |
| Predicate | shareBorderBetween |
P196422
|
FINISHED |
| Object | Germany and Austria |
—
|
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: Germany and Austria | Statement: [Bavaria and Styria, shareBorderBetween, Germany and Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareBorderBetween Context triple: [Bavaria and Styria, shareBorderBetween, Germany and Austria]
-
A.
shareBorderAgreement
Indicates that two entities have a formally recognized agreement concerning their shared border.
-
B.
sharesBorderType
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
C.
shareBorderLengthApprox
Indicates that two entities share a common boundary whose length is approximately equal to a specified value.
-
D.
shareNotableBorderRegion
Indicates that two entities share a common border in a region that is particularly significant or notable (e.g., historically, politically, or geographically).
-
E.
adjustedBorderBetween
Indicates that the boundary separating two entities has been modified or realigned from its previous position.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: April 29, 2026, 6:58 p.m.