Triple
T36801296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaji |
E909327
|
entity |
| Predicate | hasPluralUsage |
P912
|
FINISHED |
| Object | can denote multiple related Aboriginal groups |
—
|
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: can denote multiple related Aboriginal groups | Statement: [Yamaji, hasPluralUsage, can denote multiple related Aboriginal groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPluralUsage Context triple: [Yamaji, hasPluralUsage, can denote multiple related Aboriginal groups]
-
A.
hasPlurality
chosen
Indicates that an entity or concept exists or is expressed in a plural form rather than a singular one.
-
B.
hasPluralForm
Indicates that one term is the plural grammatical form of another term.
-
C.
hasPluralFamilyNameForm
Indicates that an entity’s family name has a corresponding pluralized form used to refer to multiple members of the family.
-
D.
hasPluralFormInItalian
Indicates that an entity has a specific plural form when expressed in the Italian language.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 3, 2026, 4:12 p.m.