Triple
T31206241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Group |
E795606
|
entity |
| Predicate | isCentralComplexOf |
P172545
|
FINISHED |
| Object | MIT campus |
—
|
NE NERFINISHED |
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: MIT campus | Statement: [Main Group, isCentralComplexOf, MIT campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCentralComplexOf Context triple: [Main Group, isCentralComplexOf, MIT campus]
-
A.
isCenterNontrivial
Indicates that the center of a given algebraic structure (such as a group or ring) is not trivial, i.e., contains elements other than the identity.
-
B.
isCentreOf
Indicates that one entity serves as the central point, core, or focal location relative to another entity or context.
-
C.
isSelfCentralizingIn
Indicates that an entity is equal to its own centralizer within a larger structure, meaning all elements that commute with it are contained in it.
-
D.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
-
E.
isComplexificationOf
Indicates that one entity is a more complex or elaborated version derived from another, simpler entity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 29, 2026, 9:09 p.m.