Triple
T36876879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grassmann manifolds |
E911363
|
entity |
| Predicate | hasBundle |
P192681
|
FINISHED |
| Object | universal k-plane bundle |
—
|
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: universal k-plane bundle | Statement: [Grassmann manifolds, hasBundle, universal k-plane bundle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBundle Context triple: [Grassmann manifolds, hasBundle, universal k-plane bundle]
-
A.
hasCanonicalBundle
Indicates that an entity is associated with or possesses a designated canonical bundle, typically representing a standard or primary collection of related items or resources.
-
B.
hasBow
Indicates that one entity possesses, carries, or is equipped with a bow.
-
C.
bundledStatus
Indicates that an item, service, or component is part of a bundle and specifies its inclusion state or condition within that bundle.
-
D.
hasPackageName
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
E.
bundle
Indicates that multiple items are grouped or packaged together as a single combined unit or offering.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.