Triple
T4720035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aklanon |
E104740
|
entity |
| Predicate | hasCaseMarkers |
P2130
|
FINISHED |
| Object | ang-series |
—
|
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: ang-series | Statement: [Aklanon, hasCaseMarkers, ang-series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaseMarkers Context triple: [Aklanon, hasCaseMarkers, ang-series]
-
A.
hasCaseMarking
Indicates that a linguistic element (such as a noun or pronoun) bears a specific grammatical case marking that signals its syntactic or semantic role in a clause.
-
B.
hasCase
Indicates that one entity is involved in, associated with, or characterized by a particular case, instance, or occurrence represented by another entity.
-
C.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
-
E.
hasCaseInflection
Indicates that a word or phrase changes form to reflect grammatical case (such as nominative, accusative, etc.) in a given language context.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.