Triple
T14689778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyke |
E345006
|
entity |
| Predicate | languageInWorld |
P60517
|
FINISHED |
| Object | Common Tongue |
—
|
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 Tongue | Statement: [Pyke, languageInWorld, Common Tongue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInWorld Context triple: [Pyke, languageInWorld, Common Tongue]
-
A.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
B.
isWorldLanguage
Indicates that a language is widely used across multiple countries or regions and serves as a common means of communication beyond its original native community.
-
C.
languageDiversity
Indicates the degree to which multiple distinct languages are present and used within a given context or population.
-
D.
languageUsedAs
chosen
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
E.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb5844de481908a796eaa474bfde9 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.