Triple
T29694157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M2-branes |
E751296
|
entity |
| Predicate | canEndOn |
P167608
|
FINISHED |
| Object | M5-branes |
—
|
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: M5-branes | Statement: [M2-branes, canEndOn, M5-branes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canEndOn Context triple: [M2-branes, canEndOn, M5-branes]
-
A.
canConclude
Indicates that one entity is able to logically derive or reach a conclusion about another entity or situation.
-
B.
useEnded
Indicates that an entity’s period of using or employing another entity has come to an end.
-
C.
endOf
Indicates that one entity marks the terminating point or final boundary of another entity, event, or interval.
-
D.
canBeConcludedWith
Indicates that one situation, process, or sequence is able to be finished, resolved, or brought to an end by another specified action or condition.
-
E.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:19 p.m.