Triple
T17512575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loxian |
E426484
|
entity |
| Predicate | realWorldUsage |
P46656
|
FINISHED |
| Object | primarily confined to Enya’s artistic works |
—
|
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: primarily confined to Enya’s artistic works | Statement: [Loxian, realWorldUsage, primarily confined to Enya’s artistic works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realWorldUsage Context triple: [Loxian, realWorldUsage, primarily confined to Enya’s artistic works]
-
A.
realWorldParallel
Indicates that one entity has a counterpart, analogy, or directly corresponding situation in the real world relative to another entity.
-
B.
soldInRealWorld
Indicates that the item or product is actually sold or available for purchase in the physical, real-world marketplace.
-
C.
usedInPractice
chosen
Indicates that something is actually applied or implemented in real-world practice rather than just being theoretical or proposed.
-
D.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
E.
realWorldName
Indicates that an entity’s name in a real-world context is given or associated with another value.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4525d29fc819080851bf744bc78ed |
completed | April 19, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.