Triple
T21953588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurer–Cartan form |
E542126
|
entity |
| Predicate | pullbackBy |
P93929
|
FINISHED |
| Object | left translation on the Lie group |
—
|
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: left translation on the Lie group | Statement: [Maurer–Cartan form, pullbackBy, left translation on the Lie group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pullbackBy Context triple: [Maurer–Cartan form, pullbackBy, left translation on the Lie group]
-
A.
pulledBy
Indicates that one entity is moved or drawn by the force or action exerted by another entity.
-
B.
canBePulledBackAlong
chosen
Indicates that a structure or object can be transferred or redefined along a given mapping or morphism so that it is compatible with that mapping.
-
C.
pullsTogetherWith
Indicates that one entity exerts force or effort jointly with another to draw or move something toward a common point or direction.
-
D.
returnedBy
Indicates that something is given, sent, or brought back to a previous sender, owner, or source by another entity.
-
E.
endsBy
Indicates that one event, process, or state concludes precisely at the same time another specified event, process, or state ends.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243dfb4081909bc7a722843ffea7 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.