Triple
T29694166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | isExtendedAlong |
P143966
|
FINISHED |
| Object | two spatial directions in target space |
—
|
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: two spatial directions in target space | Statement: [M2-branes, isExtendedAlong, two spatial directions in target space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExtendedAlong Context triple: [M2-branes, isExtendedAlong, two spatial directions in target space]
-
A.
hasExtendedStructure
Indicates that an entity possesses an additional or elongated structural component beyond its basic or standard form.
-
B.
isExtendedSource
chosen
Indicates that the source is spatially extended rather than point-like in the observed data or image.
-
C.
extendedIn
Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
-
D.
wasExtendedTo
Indicates that something previously existing was lengthened, expanded, or prolonged to reach a new limit, scope, or duration.
-
E.
isElongatedDueTo
Indicates that one entity becomes longer in shape, form, or duration specifically as a result of the influence or effect of another entity or factor.
- 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.