Triple
T30272544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawa |
E769842
|
entity |
| Predicate | hasNameLanguageStatus |
P21937
|
FINISHED |
| Object | local name |
—
|
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: local name | Statement: [Rawa, hasNameLanguageStatus, local name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameLanguageStatus Context triple: [Rawa, hasNameLanguageStatus, local name]
-
A.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
B.
hasLinguisticName
Indicates that an entity is associated with a specific linguistic name or label used to refer to it in a language.
-
C.
hasNameInLocalLanguage
chosen
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
D.
hasNameVariantLanguage
Indicates that a name variant is associated with or expressed in a specific language.
-
E.
hasFullNameLanguage
Indicates that the language in which a full name is expressed is associated with that full name.
- 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_69f224856d9881908c7f0dd64f059672 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 7:44 p.m.