Triple
T27794156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osu Traditional Council |
E701158
|
entity |
| Predicate | languageOfCustom |
P194299
|
FINISHED |
| Object | Ga |
—
|
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: Ga | Statement: [Osu Traditional Council, languageOfCustom, Ga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCustom Context triple: [Osu Traditional Council, languageOfCustom, Ga]
-
A.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
B.
languageOfLocalization
Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
-
C.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
E.
languageOfProduct
Indicates the language in which a product is written, labeled, presented, or otherwise made available.
- F. None of above. chosen
Provenance (4 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
| PDg | Predicate description generation | batch_69fd6a1a38f081908c573aee4696de4f |
completed | May 8, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:30 p.m.