Triple
T29694167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | isPointlikeIn |
P37462
|
FINISHED |
| Object | remaining 9 spatial dimensions of 11D spacetime |
—
|
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: remaining 9 spatial dimensions of 11D spacetime | Statement: [M2-branes, isPointlikeIn, remaining 9 spatial dimensions of 11D spacetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPointlikeIn Context triple: [M2-branes, isPointlikeIn, remaining 9 spatial dimensions of 11D spacetime]
-
A.
isPointLike
chosen
Indicates that an entity behaves or is treated as a single, dimensionless point within a given context or model.
-
B.
isPointWhere
Indicates that one entity is the specific location or point at which another entity, event, or condition occurs or is defined.
-
C.
containsPoint
Indicates that a geometric region or shape includes a given point within its boundaries.
-
D.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
E.
isWanderingPoint
Indicates that an entity is moving aimlessly or without a fixed destination within a given space 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:19 p.m.