Triple
T38564479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maonan people |
E928177
|
entity |
| Predicate | typicalBilingualismIn |
P12230
|
FINISHED |
| Object | Maonan language |
E893920
|
NE 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: Maonan language | Statement: [Maonan people, typicalBilingualismIn, Maonan language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBilingualismIn Context triple: [Maonan people, typicalBilingualismIn, Maonan language]
-
A.
bilingualismWith
Indicates a relationship where an entity possesses or is associated with the ability to use two specified languages.
-
B.
typicalBiculturalStatus
Indicates that an entity commonly exhibits characteristics or behaviors associated with belonging to and functioning within two distinct cultural contexts.
-
C.
isBilingual
Indicates that an entity is able to communicate fluently in two distinct languages.
-
D.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
usesBilingualInstruction
Indicates that an entity employs two languages as the medium of instruction within an educational or communicative context.
- F. None of above.
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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41ea8ecae88190aeb23a861f3087ab |
completed | June 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.