Triple
T33843783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alo |
E867422
|
entity |
| Predicate | hasLocalStatusLanguage |
P176357
|
FINISHED |
| Object | Futunan language |
—
|
NE NERFINISHED |
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: Futunan language | Statement: [Alo, hasLocalStatusLanguage, Futunan language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalStatusLanguage Context triple: [Alo, hasLocalStatusLanguage, Futunan language]
-
A.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
B.
localLanguageStatus
chosen
Indicates the status or condition of a language as used within a specific local or regional context.
-
C.
hasLocalServicesLanguage
Indicates that the local services available in a given context operate or are provided using a specified language.
-
D.
hasStandardLanguageNearby
Indicates that a standard or commonly used language is present in close proximity to the referenced entity.
-
E.
hasMainLocale
Indicates that an entity’s primary or default locale (language and regional setting) is a specified locale.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 1:47 a.m.