Triple
T34976053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krakozhian |
E1008679
|
entity |
| Predicate | hasApproximatePhonology |
P8038
|
FINISHED |
| Object | Slavic-like |
—
|
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: Slavic-like | Statement: [Krakozhian, hasApproximatePhonology, Slavic-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximatePhonology Context triple: [Krakozhian, hasApproximatePhonology, Slavic-like]
-
A.
hasOwnPhonology
Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
-
B.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
C.
hasPhonologicalSimilarityTo
chosen
Indicates that two linguistic elements share similar sound patterns or phonological features.
-
D.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
-
E.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:01 p.m.