Triple
T34643577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Knowledge |
E889634
|
entity |
| Predicate | hasNameTranslationLanguage |
P195088
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Sea of Knowledge, hasNameTranslationLanguage, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameTranslationLanguage Context triple: [Sea of Knowledge, hasNameTranslationLanguage, English]
-
A.
hasTranslation
Indicates that one entity is a translation or translated version of another entity in a different language.
-
B.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
C.
hasNameVariantLanguage
chosen
Indicates that a name variant is associated with or expressed in a specific language.
-
D.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
E.
languageOfTranslations
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 2:04 a.m.