Triple
T36531862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WF-WAL |
E900466
|
entity |
| Predicate | subdivisionAlternativeName |
P186034
|
FINISHED |
| Object | ʻUvea |
E51608
|
NE 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: ʻUvea | Statement: [WF-WAL, subdivisionAlternativeName, ʻUvea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subdivisionAlternativeName Context triple: [WF-WAL, subdivisionAlternativeName, ʻUvea]
-
A.
subdivisionOfName
Indicates that the given name is the name of a larger administrative or territorial unit of which the subject entity is a subdivision.
-
B.
localSubdivision
Indicates that one administrative or geographic area is a smaller, constituent part within a larger local jurisdiction or region.
-
C.
subdivisionNameType
Indicates the type or category of a named geographic or administrative subdivision (e.g., province, state, district) associated with an entity.
-
D.
subdivisionNameDivision
Indicates that a named subdivision (such as a section or unit) belongs to or is part of a larger division.
-
E.
subdivisionIdentifier
Indicates a relationship where a specific identifier is assigned to distinguish a particular subdivision within a larger entity or structure.
- F. None of above. chosen
Provenance (5 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c198c90819083eca9fcd19c29de |
completed | June 26, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.