Triple
T35530177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woleai script |
E1026776
|
entity |
| Predicate | hasPhonographicComponent |
P187423
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Woleai script, hasPhonographicComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhonographicComponent Context triple: [Woleai script, hasPhonographicComponent, yes]
-
A.
hasPhonographicType
Indicates that an entity is associated with a specific type or category of phonographic recording or medium.
-
B.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of its sound structure.
-
C.
phoneticComponents
Indicates that one entity serves as a phonetic component or contributes to the pronunciation of another entity.
-
D.
isPhonetic
Indicates that one entity represents the phonetic (sound-based) form or pronunciation of another entity.
-
E.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:04 p.m.