Triple
T3010271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German-Czech border |
E82198
|
entity |
| Predicate | hasLanguageOnSides |
P44640
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [German-Czech border, hasLanguageOnSides, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnSides Context triple: [German-Czech border, hasLanguageOnSides, German]
-
A.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
B.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
C.
hasBside
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
-
D.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
-
E.
hasSecondaryLanguage
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ccbf08190a7580c9e758804d0 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3 p.m.