Triple
T29754673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meʼphaa languages |
E752996
|
entity |
| Predicate | haveCommunityRadioBroadcastsInSomeVarieties |
P39101
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Meʼphaa languages, haveCommunityRadioBroadcastsInSomeVarieties, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCommunityRadioBroadcastsInSomeVarieties Context triple: [Meʼphaa languages, haveCommunityRadioBroadcastsInSomeVarieties, true]
-
A.
hasRadioBroadcasts
chosen
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
-
B.
usedInRadioBroadcasts
Indicates that something is employed or featured as part of radio broadcasts.
-
C.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
-
D.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
E.
hasFictionalRadioStation
Indicates that an entity includes, features, or is associated with a fictional radio station within its context or content.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 7:56 p.m.