Triple
T28718480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Elysium universe) |
E730025
|
entity |
| Predicate | alsoDepictsLanguage |
P165261
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Earth (Elysium universe), alsoDepictsLanguage, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoDepictsLanguage Context triple: [Earth (Elysium universe), alsoDepictsLanguage, Spanish]
-
A.
hasLanguageDepiction
Indicates that one entity is depicted, represented, or expressed using the language or linguistic form of another entity.
-
B.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
C.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
D.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
-
E.
presentedInLanguage
Indicates that something (such as content, information, or a work) is expressed or made available using a particular language.
- F. None of above. chosen
Provenance (4 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65706d96081909df278575e3c67f0 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:52 a.m.