Triple
T31463640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Sign Language |
E802667
|
entity |
| Predicate | hasLexiconDistinctFrom |
P12379
|
FINISHED |
| Object | Polish language |
—
|
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: Polish language | Statement: [Polish Sign Language, hasLexiconDistinctFrom, Polish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLexiconDistinctFrom Context triple: [Polish Sign Language, hasLexiconDistinctFrom, Polish language]
-
A.
hasLexiconPreservedIn
Indicates that the lexicon of one entity is preserved, recorded, or stored within another entity.
-
B.
hasDistinctVocabulary
chosen
Indicates that one entity’s vocabulary is different or distinguishable from that of another entity.
-
C.
hasLexiconSource
Indicates that a lexical item or entry is derived from, documented in, or otherwise sourced from a particular lexicon or lexical resource.
-
D.
hasDistinctOrthographyFrom
Indicates that two written forms are orthographically different from each other, even if they may represent the same or related linguistic content.
-
E.
hasLexicalDifferencesWith
Indicates that two linguistic items differ from each other in their word choice or lexical form.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 30, 2026, 9:21 p.m.