Triple
T31727241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friends in Health |
E809759
|
entity |
| Predicate | organizationalLanguage |
P51016
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Friends in Health, organizationalLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationalLanguage Context triple: [Friends in Health, organizationalLanguage, English]
-
A.
languageOfLocalOrganization
chosen
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
overarchingLanguage
Indicates that one language serves as the primary or dominant linguistic framework governing or unifying other languages or language varieties in a given context.
-
D.
لغة_الأعمال
Indicates a relationship where something is expressed, conducted, or communicated using the language of business (لغة الأعمال).
-
E.
officialTermLanguage
Indicates the language in which an official term is formally expressed or defined.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 30, 2026, 11:20 p.m.