Triple
T8684871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-theory |
E206131
|
entity |
| Predicate | nameInterpretationsInclude |
P78862
|
FINISHED |
| Object | membrane |
—
|
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: membrane | Statement: [M-theory, nameInterpretationsInclude, membrane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInterpretationsInclude Context triple: [M-theory, nameInterpretationsInclude, membrane]
-
A.
nameLiterallyMeans
Indicates that the literal meaning or direct translation of one entity’s name is given by the other entity.
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
nameIndicates
Indicates that one entity’s name signifies, reveals, or is used to denote a particular property, identity, or characteristic of another entity.
-
D.
nameAllusion
Indicates that one entity’s name is derived from, references, or alludes to another entity.
-
E.
alternativeNameMeaning
chosen
Indicates that one entity expresses the meaning or interpretation of an alternative name used for 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4aeae740819099093906ccc5f640 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.