Triple
T721064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occitan |
E14615
|
entity |
| Predicate | usesGrammarType |
P12863
|
FINISHED |
| Object | fusional language |
—
|
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: fusional language | Statement: [Occitan, usesGrammarType, fusional language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGrammarType Context triple: [Occitan, usesGrammarType, fusional language]
-
A.
hasDistinctGrammar
Indicates that the subject’s grammar system is different in structure or rules from that of the object.
-
B.
grammaticalType
chosen
Indicates the grammatical category or role (such as part of speech or syntactic function) that an expression has within a language.
-
C.
hasGrammarDifferenceFrom
Indicates that two linguistic items differ from each other in their grammatical form, structure, or rules of usage.
-
D.
syntaxBasedOn
Indicates that the syntactic structure or rules of one entity are derived from, influenced by, or constructed according to the syntax of another entity.
-
E.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58fa41c819082de2cc4e0cb2943 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.