Triple
T38581429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Skylanders element) |
E932252
|
entity |
| Predicate | hasAssociatedRealm |
P48425
|
FINISHED |
| Object | Earth elemental zones |
—
|
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: Earth elemental zones | Statement: [Earth (Skylanders element), hasAssociatedRealm, Earth elemental zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedRealm Context triple: [Earth (Skylanders element), hasAssociatedRealm, Earth elemental zones]
-
A.
associatedWithRealm
chosen
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
-
B.
hasSubrealm
Indicates that one realm or domain is a subordinate or contained sub-part of another, higher-level realm or domain.
-
C.
hasAssociatedAuthority
Indicates that an entity is linked to a specific authority that holds responsibility, control, or oversight related to it.
-
D.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
E.
hasDomainAssociation
Indicates that one entity is functionally or contextually linked to a particular domain, scope, or area of applicability.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:32 p.m.