Triple
T28945960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dindings coast |
E730577
|
entity |
| Predicate | hasUsedLanguage |
P9278
|
FINISHED |
| Object | Chinese |
—
|
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: Chinese | Statement: [Dindings coast, hasUsedLanguage, Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsedLanguage Context triple: [Dindings coast, hasUsedLanguage, Chinese]
-
A.
hasContactWithLanguage
Indicates that an entity has some form of interaction, exposure, or engagement with a particular language.
-
B.
hasWorkedInLanguage
Indicates that an entity has performed work or professional activities using a particular language.
-
C.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
hasOwnLanguage
Indicates that an entity possesses or uses a distinct language of its own.
-
E.
hasLanguageOn
chosen
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 8:40 a.m.