Triple
T23234979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lie algebroid |
E581260
|
entity |
| Predicate | anchorMapType |
P135333
|
FINISHED |
| Object | vector bundle morphism |
—
|
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: vector bundle morphism | Statement: [Lie algebroid, anchorMapType, vector bundle morphism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anchorMapType Context triple: [Lie algebroid, anchorMapType, vector bundle morphism]
-
A.
mapsType
chosen
Indicates that one entity serves as a mapping whose values or outputs are of the specified type.
-
B.
mappingType
Indicates the specific kind or category of correspondence established between two related elements or representations.
-
C.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
D.
mapsTo
Indicates that one entity is associated with or transformed into another entity, typically defining a directional correspondence or function from a source to a target.
-
E.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e8c7548190b53434eeb2620a6e |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.