Triple
T4411054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian alphabet |
E94853
|
entity |
| Predicate | ʻokinaRepresents |
P54139
|
FINISHED |
| Object | glottal stop |
—
|
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: glottal stop | Statement: [Hawaiian alphabet, ʻokinaRepresents, glottal stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ʻokinaRepresents Context triple: [Hawaiian alphabet, ʻokinaRepresents, glottal stop]
-
A.
resents
Indicates that one entity feels bitterness, anger, or lingering ill will toward another, typically due to a perceived wrong or unfair treatment.
-
B.
areRepresentedBy
chosen
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
fieldRepresents
Indicates that one field or attribute stands for, encodes, or symbolizes another concept, value, or entity.
-
D.
componentRepresents
Indicates that one component stands in for, symbolizes, or models another entity or concept within a system or context.
-
E.
representsInRelationsWith
Indicates that an entity serves as a representative or proxy for another entity within a specified relationship or set of relationships.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e4c58c8190b4190aad3095a1dd |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.