Triple
T18658816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabarchin |
E456135
|
entity |
| Predicate | hasMorphosyntacticBasis |
P132181
|
FINISHED |
| Object | Ligurian grammar |
—
|
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: Ligurian grammar | Statement: [Tabarchin, hasMorphosyntacticBasis, Ligurian grammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMorphosyntacticBasis Context triple: [Tabarchin, hasMorphosyntacticBasis, Ligurian grammar]
-
A.
hasVerbalMorphology
Indicates that one linguistic element exhibits verbal inflectional properties or patterns in relation to another.
-
B.
hasNominalMorphology
Indicates that an entity possesses a system of nominal morphology, such as inflectional or derivational markers on nouns.
-
C.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
D.
hasMorphologicalState
Indicates that an entity possesses or is characterized by a particular morphological condition, form, or structural state.
-
E.
hasEtymologicalBasis
Indicates that one term, name, or expression is derived from, based on, or historically formed from the other in terms of linguistic origin.
- F. None of above. chosen
Provenance (4 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55087ae8081909cb4c0ce6c809d55 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.