Triple
T18299655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asor Ulithian |
E438324
|
entity |
| Predicate | usedWithinCommunity |
P5924
|
FINISHED |
| Object | Ulithian-speaking community subset |
—
|
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: Ulithian-speaking community subset | Statement: [Asor Ulithian, usedWithinCommunity, Ulithian-speaking community subset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithinCommunity Context triple: [Asor Ulithian, usedWithinCommunity, Ulithian-speaking community subset]
-
A.
usedInCommunity
chosen
Indicates that something is employed, practiced, or applied within a particular community or communal context.
-
B.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
C.
usedInCommunityType
Indicates that something is utilized or occurs within a specific type or category of community.
-
D.
usesTermForCommunity
Indicates that one entity refers to or designates a community using a particular term.
-
E.
isCommunity
Indicates that an entity functions as or is classified as a community, typically representing a group of individuals connected by shared location, interests, or characteristics.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017e88cc8190a969eb628ca1b496 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.