Triple
T34154842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beilinson–Bernstein localization theorem |
E876104
|
entity |
| Predicate | hasVersionFor |
P180473
|
FINISHED |
| Object | real groups (via related localization techniques) |
—
|
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: real groups (via related localization techniques) | Statement: [Beilinson–Bernstein localization theorem, hasVersionFor, real groups (via related localization techniques)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersionFor Context triple: [Beilinson–Bernstein localization theorem, hasVersionFor, real groups (via related localization techniques)]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
C.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
D.
hasVersionBase
Indicates that one entity serves as the original or foundational version upon which another versioned entity is based.
-
E.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: May 1, 2026, 1:54 a.m.