Triple
T30892944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Many-Angled Ones |
E786949
|
entity |
| Predicate | existenceLevel |
P140003
|
FINISHED |
| Object | higher-dimensional |
—
|
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: higher-dimensional | Statement: [The Many-Angled Ones, existenceLevel, higher-dimensional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceLevel Context triple: [The Many-Angled Ones, existenceLevel, higher-dimensional]
-
A.
existenceScope
chosen
Indicates the contextual or situational bounds within which an entity or condition is considered to exist or hold true.
-
B.
exposureLevel
Indicates the degree or intensity to which an entity is subjected or exposed to a particular factor, condition, or influence.
-
C.
activationLevel
Indicates the degree or intensity to which something is currently active, engaged, or functioning within a given context.
-
D.
restrictionLevel
Indicates the degree or strictness of limitations or constraints imposed on an entity, action, or access.
-
E.
existsBecauseOf
Indicates that one entity’s existence is caused, enabled, or brought about by another entity.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923826008190931f5076cd002373 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.