Triple
T36631856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokai |
E904342
|
entity |
| Predicate | hasGrammarRelation |
P172723
|
FINISHED |
| Object | similar to Madi 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: similar to Madi grammar | Statement: [Lokai, hasGrammarRelation, similar to Madi grammar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrammarRelation Context triple: [Lokai, hasGrammarRelation, similar to Madi grammar]
-
A.
grammarRelation
chosen
Indicates a grammatical relationship between linguistic elements, such as how words or phrases function or depend on each other within a sentence.
-
B.
hasGrammarFrom
Indicates that one entity derives or uses its grammatical structure or rules from another entity.
-
C.
hasReferenceGrammarBy
Indicates that an entity is associated with or described by a reference grammar authored or compiled by a specified agent.
-
D.
hasReferenceGrammar
Indicates that an entity is associated with or described by a specific reference grammar resource.
-
E.
hasGrammar
Indicates that an entity possesses, follows, or is associated with a particular system of grammatical rules or 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.