Triple
T12315704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcrist |
E293593
|
entity |
| Predicate | languageOfAlias |
P63334
|
FINISHED |
| Object | Common Speech |
—
|
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: Common Speech | Statement: [Orcrist, languageOfAlias, Common Speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAlias Context triple: [Orcrist, languageOfAlias, Common Speech]
-
A.
alternateLanguageName
chosen
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
B.
languageOfLocalization
Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
-
C.
languageOfField
Indicates that a particular language is used as the primary or relevant language within a specified field, domain, or area of activity.
-
D.
languageOfTranslations
Indicates that one entity is the language into which another entity (such as a text or work) has been translated.
-
E.
languageEquivalent
Indicates that two linguistic expressions convey the same meaning or function across different languages or language varieties.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.