Triple
T20059767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taifun |
E499436
|
entity |
| Predicate | relatedEnglishTerm |
P28329
|
FINISHED |
| Object | typhoon |
—
|
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: typhoon | Statement: [Taifun, relatedEnglishTerm, typhoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEnglishTerm Context triple: [Taifun, relatedEnglishTerm, typhoon]
-
A.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
B.
languageEquivalent
chosen
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
-
C.
languageTerm
Indicates that one entity is a linguistic expression (word, phrase, or term) used to denote or label the other entity.
-
D.
cognateOf
Indicates that two linguistic forms share a common historical origin, typically descending from the same ancestral word.
-
E.
linkedToLanguage
Indicates that an entity has an association or connection with a specific language, such as being expressed in, related to, or dependent on that language.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66374f4a48190beb575a6c84ebdb4 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.