Triple
T12932731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phrygian language |
E309422
|
entity |
| Predicate | usesCaseEndings |
P13618
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Phrygian language, usesCaseEndings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCaseEndings Context triple: [Phrygian language, usesCaseEndings, yes]
-
A.
usesCaseHarmony
Indicates that one element selects or governs another element such that their grammatical cases are compatible or harmonized according to the language’s case system.
-
B.
usesCaseSystem
Indicates that one entity employs or operates using a particular case system (e.g., grammatical or structural case-marking system).
-
C.
nameEnding
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
D.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
E.
hasCaseForms
chosen
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
- 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:42 p.m.