Triple
T2893168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorbian languages |
E63873
|
entity |
| Predicate | usedInSignage |
P5950
|
FINISHED |
| Object | bilingual signs in parts of Lusatia |
—
|
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: bilingual signs in parts of Lusatia | Statement: [Sorbian languages, usedInSignage, bilingual signs in parts of Lusatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSignage Context triple: [Sorbian languages, usedInSignage, bilingual signs in parts of Lusatia]
-
A.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
B.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
C.
signageStandard
Indicates that something conforms to, follows, or specifies a particular standard or convention for signage.
-
D.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
E.
usedInDigitalMedia
Indicates that something is employed, featured, or incorporated within digital media content or platforms.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe062234c81909411e34db7d2683d |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:07 p.m.